• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1020
  • Last Modified:

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

Hi,

I am receiving this message after stop a brekpoint in the Form. If I have a breakpoint in the module and stop, it doesn't crash the VB.

Here are the dlls I got from Process Explorer when the VB crashes:

gridex20.ocx (package)
faultrep.dll (new object)
ieframe.dll.mui (deleted object)
olepro32.dll (deleted object)
winsta.dll (new object)
wtsapi32.dll (new object)

This error only happens with one specific project.

Thank you in advance.
0
DistillingExperts
Asked:
DistillingExperts
  • 5
  • 2
  • 2
  • +1
1 Solution
 
DistillingExpertsAuthor Commented:
Anyone?
0
 
bright12Commented:
Can you supply some more information? What is the purpose of the script? And if you remove the breakpoint, will it crash?
0
 
puppydogbuddyCommented:
Post the code for the Sub procedure involved in the crash.
0
Cloud Class® Course: Microsoft Windows 7 Basic

This introductory course to Windows 7 environment will teach you about working with the Windows operating system. You will learn about basic functions including start menu; the desktop; managing files, folders, and libraries.

 
DistillingExpertsAuthor Commented:
It only happens in the Form and not in the Module. In any Form. No sub procedure specific.
0
 
bright12Commented:
So what you are saying is that when create only a form and run this VB is crashing?
0
 
DistillingExpertsAuthor Commented:
No, The existing project has many forms and many modules. If I break point in the module and it stops the execution in the break point and then I select to stop it in the button, it will not crash. However, if I do the same in any form, it will crash.

I have done the same in others projects and didn't crash the VB.
0
 
puppydogbuddyCommented:
try to determine what is different about this project.  
   Different version of ms access?
    Missing vb library references?
          etc
0
 
Genetic_WolfCommented:

I didn't check all object you're referencing but winsta.dll is using some sub classing method wich is very bad in Vb and CANNOT be interupted.  Could even make a BSOD occur

The only secure way to use subclassing in Vb is to DEACTIVATE IT when debuging.
and would be though to do if you're using a DLL.

I prefer to sub class inside Vb at all time since it give more control over it.

you cannot use IDE DEBUG mode WHILE your form is subclassed.
0
 
DistillingExpertsAuthor Commented:
Hi Genetic Wolf, I will do this test as soon as time permits.
0
 
Genetic_WolfCommented:
do you confirm your form was subclassed ?
because if so, like I said, you cannot debug in the IDE while subclassed.
0
 
DistillingExpertsAuthor Commented:
I will be back to this near the weekend. Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 5
  • 2
  • 2
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now