VB Watch - How to use

How to handle run-time errors with VB Watch

No matter how carefully you designed your code, unexpected errors will occur. If you don't care about proper error handling, you merely get a message box like "Division by zero" before your application terminates, leaving your customer helpless and angry, while your development team has no clue what happened.

Visual Basic does provide tools for error handling. The On Error and Resume statements allow you to build local error handlers. Want know the line the error occurred on? Then add line numbering to all of your code. But who has the time to do that manually?

VB Watch automates error handling. Write once, use many. VB Watch adds error handlers right before compilation, and the original source is left intact. VB Watch instruments each procedure with your own error handler and adds line numbering. Already have some error handlers - no problem. The handlers are fully customizable, making you ready to provide localized error messages, perhaps with further instructions who to contact.

If and when a run-time error occurs, VB Watch gives the user the ability to email you the full program status in a single file. The information includes:

  • Exact location and description of error
  • Contents of variables, including arrays, fields of user-defined types and properties of objects
  • Description of the user's system
  • Versions of run-time libraries installed
  • Call stack and parameter values
  • Execution trace, even line-by-line
  • Screenshot

Imagine fixing bugs with all of this at hand! You'll fix even the toughest bugs in record time. VB Watch turns errors to an opportunity to make your customers real happy!

How to test and profile code with VB Watch

Argh - my code is too slow! Where are the bottlenecks? Don't waste the users' time, use VB Watch Profiler. Measure how much time your application spends and where. Find the problematic areas - if it's those nested loops, the file access or that absolutely strange line of code. After you've fixed it, check out just how much faster you managed to make it.

How do I reduce the number of bugs shipped? With proper testing, of course. How do I know if I've tested enough? Stop guessing - let VB Watch record the test sessions. VB Watch reports which lines you have executed and which ones need more attention. Use this information to ensure 100% test coverage.

How about testing and debugging large systems with controls, libraries and executables all in action simultaneously? VB Watch Debugger sees inside compiled code. Take a look at the execution trace, call stack and objects instantiated. Set up breakpoints within exe's, ocx's and dll's. Find those bugs that only occur on that special computer when that special ActiveX control is instantiated.

Test and profile your programs before release. In the long run, you'll save a lot of time and money. Start saving, download and try VB Watch today!


A fully functional demo of VB Watch is available. It is limited to projects with max 10 source files. The full version has no such limitations.

Go to download