>>>>Does it matter that it specifies my default printer, what if someone else uses a different model?

>>>That issue is taken care of when you edit the EXPR, TAG1 and TAG2 fields. (Just before compiling the reports into the app, or just before distributing the reports with the app. If you don't know what I mean by that, search for recent messages about those fields, or messages talking about removing printer specification from a report form.)
>>>
>
>The following information is straight from the Virtual FoxPro User Group (http://www.vfug.org) tip list.
>
>Have you ever noticed that when you create a report it prints out just fine and when you deliver it to a client's site is bombs!?!?!
>One possible reason is because FoxPro (most versions) embeds the current printer driver in the report file at design time. One way of correcting this problem is to open the FRX file as a Table (yep, most system files are actually table files & can be opened as such & edited). Then look in the fields for your printer driver setup. Once you find it (it is usually in the first row) you can just delete the contents of this field, save the table and close it. Then try printing again.
>
>With the contents of the printer driver field deleted FoxPro will usually just use the current print driver used by the system.
>
>Just remember to back up your files first just in case!!!
>
>
>
>It works in VFP 3.0, 5.0, and I assume 6.0. Just take that last line to heart: backup before you try this.

Bill, I will try it. Is the field you refer to called tag2?