> You may want to stick to non-graphical reports (ASCII) and send straight dumps to the printer everytime. Wouldn't that solve the problem?

Wayne,
I don't think so. I tried it out, but then I read the VFP help file about the ASCII flag.. Here's a snipppet:

---
TO FILE FileName2 [ASCII] Specifies the text file to which you send a report. The current printer driver is used when the report is sent to the text file. The file created when you include TO FILE has the default extension .TXT.

You can include the optional ASCII clause to create an ASCII text file from the report definition file. Without the ASCII clause, PostScript and other printer codes are written to the text file. Any graphics, lines, rectangles, or rounded rectangles in the report definition do not appear in the ASCII text file.
---

So even if you save the report to an ASCII file, the current printer driver still plays a role in how the text is formatted.

I'm thinking that it may be possible to install the Windows "Generic / Text printer" driver on each machine, and then eliminate the boxes in the report form. (maybe replace them with lower-ASCII symbols, like ---- or _____ )

If anyone has any words of warning relating to the generic windows printer, I'd certainly like to hear about it.

Thanks!