>I can run this code in VFP 9 SP1 and VFP 9 SP2 and I don't get any error about loading a printer driver. Check to see if you have the printer environment stored in the report .. if so .. uncheck the Printer Environment option. Maybe that is interferring.

The printer environment is definitely NOT saved, in the Test report or in the client's CaseSum0 report. In fact I've tried saving it with the Test report and it doesn't have any effect upon the generation of the error.

>When you omit the ASCII keyword or use Visual FoxPro's object-assisted output mode writes PostScript or other printer codes to the text file along with the content of your report. To create an ASCII text file from the report definition file, SET REPORTBEHAVIOR 80 and include the ASCII keyword.

>Note
When you include the ASCII keyword, you can process a report on a computer that has no printer driver setups installed. Without the ASCII keyword, a REPORT FORM command issued on a computer that has no printer driver setups installed generates an error.

Yes, I have read this section of the Help file. It's where I got the idea to experiment with Set Reportbehavior and the ASCII clause in the first place. Fortunately for me, in this situation it doesn't matter whether the print file has printer control codes or not so using the ASCII clause is a very viable option. But if I every DO need a file with print control codes (and one of my VFP 7 applications uses this feature extensively), I'm in trouble because the command simply doesn't work in this environment. Regardless of the report or the data and whether the command is sent either from a program or from the command window, it always generates an error.

Since you don't observe this, it is possible that my specific printer's driver could factor in somehow. This is a 3-month old HP model that works perfectly with all other applications and when sending reports to Preview or To Print. I only have one printer installed on this workstation so can't test that hypothesis here, butI I will do that when I am back in the office next week.