Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Emergency. VB6 Crash and burn

Status
Not open for further replies.

thornmastr

Programmer
Feb 2, 2002
1,337
US
i have an emergency situation and could use a bit of assistance and or some clarifying suggestions. This is the problem. Create a new form with a number of text fields, labels, and command buttons. Nothing out of the ordinary. Save the form. VB 6 gives you the nasty message “Visual Basic has encountered a problem and needs to close.”
Or, it allows you to save the form, and then when you double click on the form, you get the same hideous message, you don’t send the infamous error report to M$, and VB dies in quiet agony.

Background Information.
1) Using Visual Basic 6.0 Enterprise Edition.
2) Not using Visual Source Safe
3) Developing Under XP PROFESSIONAL.

What I have learned:

1) I have learned I can just create a blank form and that will save and reload without any problem. I can add one text box and one label and in most instances it can be saved and reloaded a number of times before it develops the nasty message, then die but eventually it will happen.
2) Creating a form with one text field and one command button will immediately force that message abort condition.

What I have done to try to find a solution.

1. Removed VB6. Reinstalled VB6. Problem still exists.
2. Used very small form names and variable names. No help.
3. Created a new folder. Moved project and all associated files into new folder including project name. Did not solve problem.
4. Started entirely new project and copied forms and modules into new project. Problem still occurs.
5. Learned that adding a new text field to an already existing problem did not cause the problem, but…..
6. Adding a command button to an already existing form immediately caused the problem.

I an hoping someone has experienced this before and knows what the real solution is or at the lest has some good ideas to get rid of the problem.

Thank you for your help.




Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@earthlink.net
 
I had a similar problem I think, which went away again I think when I ran service pack 5. My symptoms were when I opened a form to work on it, if I observed closely my mouse curser went to a cross. I would then know if I clicked my mouse on the form I would get the having to close notice. I always knew it was going to crash by the curser shape of the mouse. It may be totally different to your problem, but as I said touch wood, thank God I have not seen it again. I know I rebuilt forms from what was left, and it would be okay for a while and then zonk, just when I didn't need it. Keep my fingers crossed someone else has the answer for you. Regards
 
This is probably no help to you at all but I found that I got a similar problem if I had too many objects selected at the same time.

Have you tried using a different machine?

Does it still do that if you create the objects "on the fly" - I think it's the createobject method that allows you to programmatically create buttons or textboxes during the programs run time.

Instead of removing and reinstalling VB6 - I'm wondering if you can install a second vb6 on your pc (never tried myself) and if so does the problem persist?

Sorry I can't be more help....
 
Zor,

I am running SP 5. I get an hourglass when i attempt to open the form. It lasts for about 20 seconds and the error message pops and that's the end of everything.

Tom, The form only has four controls; 1 label, 1 text box, and two command buttons.

I really prefer to build my forms in the IDE. I guess, if this situation does not improve by Tuesday I may not have a choice.

Thanks to the both of you for your input.

Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@earthlink.net
 
Sorry Robert I could not help. Tom I think you are talking about the stupid closedown you get if you are highlighting/selecting several objects and happen to click again on a same control again. The only way to overcome that is by making sure the properties window is open, an MS admission.
 
I resolved the issue. Everything is back to normal,the problem is gone. Unfortunately the resolution did not allow for finding the problem nor in understanding anything which led up to the problem.

XP allows you to reset your system settings to a previous date. I set them to the day before the problem began and now everything works just fine. For such things I am greatful. It would have been nice if I coud have found an explanation but obviously that will not happen.

Robert Berman
Data Base consultant
Vulcan Software Services
thornmastr@earthlink.net
 
Glad you got round the problem. Lets hope it stays away, nobody wants headaches like that. Regards
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top