Wow - that's a GREAT idea for an enhancement. Let's tell MS to have the debugger highlight a bad line of code. Pretty subjective, but computers are getting smarter......

Jokes aside, learning to use the debugger is worth the time and trouble. The Trace window shows your source code for the active PRG or Method. The Watch window can be used to keep an eye on variables, and the Locals window shows the property values and variable values for everything 'live'. There are also Break windows, CallStack and Debug Output areas, but they're for later. < grin >

The easiest way to try it out is to use it on a method you wrote yourself. Then you can follow the code, look at variables, etc. When you have a little idea of how it works then you can try it on source code from your framework or application object. Buttons at the top allow you to resume running code, cancel the prg/method, step through one line at a time, step over a method/prg/function, step OUT of a method/prg/function, etc. Try it out.

By the way, NOBODY likes to track errors in Wizard source code. So don't be surprised if it takes a while.


>Hi Barbara.
>
>I followed your last post to the letter. I placed the code you suggested in the click event of the add buttonset and typed "set asserts on" in the command window.
>
>When I tried to add a new record in the child the debugger popped up, but to be very, very ,very honest, I do not know what I am looking for.
>
>Can you give me a little instruction with how to use the debugger to find my problem (not being able to add more than one record to my child)?
>
>Will I know I have found the leak when I stumble across it in the debugger, or will I have to recognize a piece of code is missing or a piece of code is not correct. Will something be highlighted indicating I have made a gross error?
>
>Thanks for your time Barbara..
>
>Jason