Unload Form does not always terminate program execution
I've seen several cases where all of the forms in my app are closed, yet dialog boxes still pop up, indicating a problem.
This makes the users feel uneasy :-)
What is the proper way to COMPLETELY terminate execution in a VB app, after all the forms have been unloaded ?
Triggering / de-triggering the code !
It seems like the original coder failed to apply any " Exit Do " statement's
within your Looping structure's
Apply : " Exit Do " ' in your Loop's < This should basically be your pivot point ,
Apply : " Do Events "' Between your Loop's < this will allow Windows to destroy
If Button = 1 then
' Your program during the Unload Event
The use of " End " in the Unload Event just forces Windows to crash exit the application , leading to an internally messy destroy .
If there is any Blitting then more than likely the original coder failed to include the necessary " Destroy DC " , in which case Windows is still trying to write into memory .
Really just guessing here , don't really know what the structure is.....