ExitProcess() I guess. Well, that's only possible if you want to kill the entire application. I might do this if the module is an exe, but it's less handy because I can't use all kinds of set variables and opened tables.
>not fully on topic - in one large app scenario we skip form destruction if shutdown event is asked for -
>we walk all forms to close tables, but then kill process while 0..n forms may still be instatiated. Best optimization is to skip running unneccessary code ;-)
>
>>The formclass I recently developed can have as much as over 1800 objects. What strikes me is that it builds the form in a snap, but it requires almost a minute to 'destroy'.
>>There's no special, time consuming, code in any Destroy(). And only some have some code in their QueryUnload() or Release().
>>Who knows of any trick to speed up the destruction of the form?
>>Perhaps it's the fact that a subset of those objects have properties that refer to other objects? Hmm, I'll gonna try this out.
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
