>I'm sure I'm missing something, but I cannot get an "on error" routine to trap run-time errors which occur during a "report form" call. The specific problem I've run into is a "printer not ready" dialog box with a title of "Visual FoxPro" and an "OK" button. [The printer BTW is an HP4000 with 40 mb of internal ram, using the latest HP driver and configured on an NT 4.0 SP 6a network print server. Output is spooled and, until our hardware guy added a couple of new color printers to the print server, I had never seen such an error on this network.] I'm running VFP 5 but see the same problem with VFP 6.0 SP3.
>
>I've tried adding "on error" calls into the report's methods (exposed in the Data Environment properties) with no luck. My sense is that, once the report form has completed its INIT method and actually launches itself, all error trapping is turned off until the report form executes its DESTROY method and returns control to the calling program. Is that the case?
>
>I'm not looking for ways to get the network from eliciting the error (which is probably a network configuration issue) so much as I'm looking for ways to trap all types of errors - variable not found, operator mismatches, etc. - which can and do occur when executing a "report form" command. Your ideas and experiences would be helpful.

You can't do error trapping in reports, period! End of sentence. Try using a printer driver that was supplied with Windows, as the HP drivers are terrible!