At 10:08 AM 7/15/2015 -0400, you wrote:

>> > In one of these cases, the user starts the query in a modal child window,

>> > and therefore should not be able to click the "x" close button or the

>> > upper-left-corner popup-menu button to trigger QueryUnload(). So that's

>> > another headache.

>> >

>

>I was able to talk to the user involved in this one. He says he used that

>modal window, finished with it, closed it, and pressed the "X" button in

>the main window to shut down the application. If so, why was the process

>controlled by the modal window still in the stack trace when Error 3 was

>triggered during the shutdown?

I will just add that after several tries, I am unable to use the visual

interface in my application fast enough to start a query operation and then

do something that interrupts it and causes an error. Every time I start a

query and then, as fast as I can, close the window I started it in or close

the application before it returns results, the thing just forgets it was

running a query and proceeds normally to do what I asked it to do. So it is

just surpassing strange. I cannot imagine what someone could have done to

get these results.

Ken

_______________________________________________

Post Messages to: ProFox@leafe.com

Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox

OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech

Searchable Archive: http://leafe.com/archives/search/profox

This message: http://leafe.com/archives/byMID/profox/5.2.1.1.1.20150715110723.020ad7b8@POP-Server.stny.rr.com

** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.