Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 286
  • Last Modified:

Visual basic has encountered a problem and needs to close. We are sorry for the inconvenience

Hi,

Every time I do a breakpoint and then after I see the content I stop the debugger, VB gives me this error.

Any idea?
0
DistillingExperts
Asked:
DistillingExperts
  • 10
  • 10
1 Solution
 
CluskittCommented:
Possibly something is corrupt. Try to reinstall, or, if necessary, uninstall/reinstall.
0
 
DistillingExpertsAuthor Commented:
I did that but didn't work.
0
 
CluskittCommented:
Does it happen only on one project, or any project you do? Have you tried starting a simple Hello World project to see if the same happens?
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
DistillingExpertsAuthor Commented:
Others projects work. However, couldn't fix the problem yet.
0
 
CluskittCommented:
Try copying the code (only the code), create a new project, insert the same objects and paste the code. It's possible that your project file became corrupted, or even the resources file. If you do that and it stops happening, you know that's the reason.
Also, it might be worth running a chkdsk, just in case some drive malfunction caused the corruption.
0
 
DistillingExpertsAuthor Commented:
I opened it in another folder extracting from the version control and got the same error.
0
 
CluskittCommented:
I'm inclined to think it's one of the project files that got corrupted. Seeing as it only happens on that project, I would delete and start over. You may copy the VBA code, as that isn't likely to be the cause, rather a form, resource, control, etc.
0
 
DistillingExpertsAuthor Commented:
But it worked before and in the source control should be fine as I never did a check-in. I don't think it is corrupted, even though it seems.
0
 
CluskittCommented:
Well, I found some more tests for you to do. First, download microsoft's process explorer and check for any "foreign" or useless processes. Also, try to monitor your VBA process to see if you can find out what is crashing it.
Also, and this may seem silly, try opening the project through File->Open Project and testing, then double clicking the file and testing.
Also try to unload any add-ins you might have.
0
 
DistillingExpertsAuthor Commented:
How can I monitor my VBA process? The only thing it started in the Process Explorer is dwwin (Dr. Watson).
0
 
CluskittCommented:
You have to select the VB handling process, then on the lower window check handles or dll's loaded. Try to see anything unusual that you don't see on other projects.
If you can't see the lower pane, you can activate it in: View->Show Lower Pane (shortcut key: Ctrl+L)
To see lower pane on DLL mode, View->Lower Pane View->DLLs (shortcut key: Ctrl+D)
To see handles, View->Lower Pane View->Handles (shortcut key: Ctrl+H)

Try to see if you can pinpoint what is causing the crash.
0
 
DistillingExpertsAuthor Commented:
I did all you have said but still cannot find the point where it crashes. The only thing I know is that only happens in the Forms breakpoints, not in the modules ones.
0
 
CluskittCommented:
Well, other than it being a corrupted control/resource file/etc, I don't really know what could be causing it.
As I said, you could know for sure that's what it is if you create the project again and implement everything again (manually, not importing). It will be a lot of effort (depending on project size), but if your project generates that error, there's no trusting the computations it's making anyway.
0
 
DistillingExpertsAuthor Commented:
It only breaks on the debug. Really no more info?
0
 
CluskittCommented:
I ran out of ideas. Ask for attention, and get added to more areas. Add the XP area (I'm assuming it's your OS, if not, add that one), at least. Maybe the Mod will have other ideas.
0
 
CluskittCommented:
That is, ideas for areas. :)
0
 
DistillingExpertsAuthor Commented:
You know what scared me.. only you answered out of all the people here. It seems that only you are specialist the another ones just look into the google.
0
 
DistillingExpertsAuthor Commented:
Does it give you any hint on what my problem might be?
http://forum.codejock.com/forum_posts.asp?TID=10773
0
 
CluskittCommented:
I was the only one that answered, probably because it's a very unusual case and one more focused on the OS than the language itself. Usually experts that monitor the VB6 area are more into coding than IT maintenance.

As for the link, it's still too generalized. Some were the code that crashed it, others had a different problem. Each with his own solution. I don't really know what could be causing it, especially since you say it only happens on that project and none else. I assume you tried the solutions in there, so there really isn't much I can add that I haven't said already.

I do advise you to add some areas to your question, so different types of expert can join in. The XP/Vista/7 area seems like a good place to start.
0
 
DistillingExpertsAuthor Commented:
I will close this one and open another with more details. Thanks a lot.
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 10
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now