>Or call it "troubleshooting the troubleshooter" Dr Watson
>
>Is there a way to disable him? He seems to be picking up errors in my vfp6 app that either don't exist, or may exist, but I'm not able to trap or debug because he grabs them first, and then shuts down vfp.
>
>I can't even tell which it is...

From Windows Help:

The system looks in \\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug
for the values named Debugger and Auto. The Debugger value shows the name of the debugger specified to analyze application errors. If the Debugger value is found, the system checks to see if the Auto value is set to zero or one.
If Auto is set to zero, the system generates a message box that advises you that an error has occurred in the application. If the Debugger value contains the name of a valid debugger (such as WinDbg or NTSD), the message box will have two buttons: OK and Cancel. If you choose the OK button, the application is terminated. If you choose the Cancel button, the debugger specified in the Debugger value is started. If the Debugger value is empty, the message box will have only an OK button and no debugger will start.

If Auto is set to one and a debugger is specified in the Debugger value, the system does not generate a message box before automatically starting the debugger.
When Windows NT is set up on your system, the Auto value is set by default to one and the Debugger value is set to DRWTSN32. This means that when an application error occurs, Dr. Watson for Windows NT will automatically diagnose the error and log the appropriate diagnostic information.
If you have been using a different application as your default debugger, and you want to use Dr. Watson instead, go to the command prompt and use the command drwtsn32 -i to start Dr. Watson. The -i switch causes the necessary changes to be made to the Registry.