>Hi Brett. I understood that. :-)
>
>If you intercept all errors, you can write it into a table so that you won't have to read the VFP error diallog. I would imagine your developer is debugging an application that he/she is working on and is running modules. Just make sure that your custom error handler is invoked.
>
>If it is errors that your developers are typing in the at the VFP command window, then I think you might be able to have your custom error handler running also. When the developer starts up VFP they could just type in
>
>ON ERROR do form c:\brettstools\errorform
>
>This form could then display the error. It seems that this should work.
>
>You would then have no errors displayed with the default VFP error diallog.
>
>Does this make sense?
>
>>Hello Evan, I must have not made myself clear. The error box that is blacked out is the one VFP puts up not me. Say you go to your command line and type 'CUBS WIN'. You will get (or should get) a VFP error box come up that states 'Unrecognized Command Verb' with two buttons that are OK and HELP. Well what some of my developers get and this is only sometimes is a box that is blacked out where the message should be. So they cant tell what the error was and this makes it hard to debug. Hope this clears it up.

Yes it makes sense, but they still would like to know what the messages are being blacked out. They all have VFP 6.0 and SP3. I can only assume a video driver problem at this point and they updated their drivers and this did not help.
Thanks for the help