>
> If you haven't read it already, there is a section in the Dev Guide about using the debugger that gives a decent overview. Basically, you want to use the "Step Out" button to return you to the routine that caused the error. From there you can view variables, step through the code, etc. If I'm trying to figure out an error I'll usually add a SET STEP ON right before the error occurs. Sometimes I'll even move it back a bit further so I can watch everything else leading up to the error. For example, if I'm getting an error when adding a new record I'd add something like:
>
>SET STEP ON
>DODEFAULT()
>
>to the Click() method of the Add button.
>
>Then I'll step through all the code until the error occurs.

Paul,

Speaking of errors, did you figure out what was causing the duplicate primary keys in your code?