Oddly enough, this is exactly what I was doing. It worked in one form but not in the other. The errant form displayed the default printer on most (perhaps 55 of 60) workstations but the remainder showed an odd assortment of different printers. Yesterday it happened to me here on my network. I recognized the printer as a local device I'd been using at one of the client's remote offices when a specific report was last modified. Sure enough, I found printer information in tag and tag2 of the .frx matching that printer. After removing the references and recompiling the exe, there have been no new reports of the problem (but it's only been one day <g>.)

The really odd thing is that it wasn't the same printer appearing for each of the affected workstations. It is as if Windows (or VFP?) selected a printer from those installed that was similar in some way to one referenced in the .frx. That made the problem very difficult to diagnose.

Thanks to you and to Simon for your suggestions. The input was most helpful in urging me to think "outside the box."