Link to home
Create AccountLog in
Visual Basic Classic

Visual Basic Classic

--

Questions

--

Followers

Top Experts

Avatar of DistillingExperts
DistillingExperts

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.

Zero AI Policy

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Avatar of DistillingExpertsDistillingExperts

ASKER

Anyone?
Avatar of bright12bright12🇳🇱

Can you supply some more information? What is the purpose of the script? And if you remove the breakpoint, will it crash?
Avatar of puppydogbuddypuppydogbuddy

Post the code for the Sub procedure involved in the crash.
Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

Avatar of DistillingExpertsDistillingExperts

ASKER

It only happens in the Form and not in the Module. In any Form. No sub procedure specific.
Avatar of bright12bright12🇳🇱

So what you are saying is that when create only a form and run this VB is crashing?
Avatar of DistillingExpertsDistillingExperts

ASKER

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.
Free T-shirt

Get a FREE t-shirt when you ask your first question.

We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.

Avatar of puppydogbuddypuppydogbuddy

try to determine what is different about this project.  
   Different version of ms access?
    Missing vb library references?
          etc
Avatar of Genetic_WolfGenetic_Wolf


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.
Avatar of DistillingExpertsDistillingExperts

ASKER

Hi Genetic Wolf, I will do this test as soon as time permits.
Reward 1Reward 2Reward 3Reward 4Reward 5Reward 6

EARN REWARDS FOR ASKING, ANSWERING, AND MORE.

Earn free swag for participating on the platform.

ASKER CERTIFIED SOLUTION
Avatar of Genetic_WolfGenetic_Wolf

Link to home
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Create Account
Avatar of DistillingExpertsDistillingExperts

ASKER

I will be back to this near the weekend. Thanks.
Visual Basic Classic

Visual Basic Classic

--

Questions

--

Followers

Top Experts

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.