Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Was there a firing order change?
Message
General information
Forum:
Visual FoxPro
Category:
Other
Miscellaneous
Thread ID:
00885695
Message ID:
00885841
Views:
12
>In 8, this doesn't happen for #3. It is almost as though it completely skips the QueryUnload()/Release() events for the form when #3 happens and goes straight to the Unload. I have tried to bind the QueryUnload of _screen to the form's. This is trashed the instant I make a change. Am I missing something or doing something wrong?

I haven't noticed changes, as I do things differently. But I do know that these 2 events' firing all depends on how the form-closing is done, at least in vfp8. For example:

1) You click the 'X' button to close form, you fire only Queryunload.

2) You have a "Close" button with "thisform.release" and only the Release fires.

Have you put WAIT WINDs or Messagboxes in the 2 events, to be sure what's actually firing?

Anyway, my own method (there are several) for dealing with form-closing situations (a bit over-simplified here) is to have a "Nodefault" in Queryunload, and then fire the Close/Exit button Click from Queryunload after this. This Close/Exit button has a Thisform.Release call, among other things, and ensures the same firing sequence no matter what "close" method is used (except a crash, maybe I should add).
The Anonymous Bureaucrat,
and frankly, quite content not to be
a member of either major US political party.
Previous
Reply
Map
View

Click here to load this message in the networking platform