How Can I Catch An Exception(Inner VB Or Dll Error Calling WIN32 API) Regardless Of A Concrete Sub Or Function In VB6.0

Question

0.00/5 (No votes)

See more:

As we all know, we can catch a runtime error in VB6.0 using this statement —— "On Error GoTo ...". However, if I programm in this manner, I have to write a lot of similiar code in each Sub Or Functon. I consider it time-consuming and really boring! So,here comes a question, "Can We Do It All In One Sub Or Function Or Even In Another Process(like "BugReport.exe")". I very much prefer starting a new process to record detailed runtime parameters of my target process and save them to a log if necessary, but I am a beginner of Programming With VB. So, can anybody give me some pratical suggestions? Much appreciated!

Posted 15-Nov-13 21:40pm

Don.Coleone

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

CHill60 · Accepted Answer · 2013-11-16T05:07:00

To blindly answer your question I can direct you to this old article[^]

You could have the error handling in a completely separate activeX dll if you really wanted to ... see how to create an activeX dll[^], but you're probably better off just having the centralised error function in a separate .bas module to be included in your projects.

Having said all that ... you do realise that VB6 is no longer supported?

Unless there are constraints (such as the corporation you work for already has a code base in VB6 and you have to continue to maintain it), then I would advise you to "upgrade" to a .NET language. The Express versions are free (unlike VB6) - http://www.visualstudio.com/downloads/download-visual-studio-vs[^], will have greater longevity, and have better error-handling capabilities