I use VB6 with SP6 and Jet databases. when I close the last form I get the message "Visual Basic encountered a problem and needs to close. We are sorry........ Contact Microsoft". I no longer contact Microsoft because I do not get any feedback or advice. The problem comes and goes and I don't know what causes it or what makes it go away. Can anybody help?

before you started encountering this problem... have you made any new installations? changed any registry keys? etc etc etc? do you also have missing components that the program is supposed to have access to? stuff like that..

done any?

____________________________
Been busy trying to take a second degree <--it's not working out...

Yes, I have installed and uninstalled programs but can't ID any connection. VB falls over after executing all of the code in the Form_Unload event.

do you mind sharing the code in your unload event?

____________________________
Been busy trying to take a second degree <--it's not working out...

I don't mind sharing my code  - but I have determined that he crashing has nothing to do with the exit routines.

I have spent hours whittling the problem down to the fact that all proceeds well as long as I do not change the order in which the frames on the form are stored.

I got there by restoring the system from backup then adding code, backing up and running the job.

The form has many frames which I make visisble and invisible as required depending on which tabs are selected in a tab control. If I save the code after bringing to the fore a frame which was behind others, VB crashes when the form unloads. If I restore the .frm and .frx files to the previous version before changing the frame order, add the new code but save the project with the frames in the unchanged sequence, no crash occurs.

Please help as this is a method of 'limping' along when, in fact, this project should be screaming along to an already very delayed finish. I do not know what lies ahead to bite me if this problem is not fixed soon.

Thanks for your assistance and interest

I have a similar problem with the VB5 development environment (Enterprise edition), with exactly the same message. But it doesn't seem to affect any code created or compiled in the environment, so I have ignored it.