>Correct me if I am wrong, but it really only has to be done once, just before you do the final compile of the app that you are going to distribuate(sp?). If you were clever (and I am NOT) you could probably even make a hook in the project so that on build, it will open all the .frx's and zap those fields.
>
>>Todd...
>>
>>Well, that's what I was afraid of. :) We're heading down that path, but I was hoping to avoid it.
>>
>>Scott
>>
>>
>>>Scott,
>>>
>>>There have been a few articles kicking around about this. Basically, you need to use the .frx as a table and delete the contents of the "tag" fields.
>>>
>>>>A clarification:
>>>>
>>>>To summarize: If an FRX fails to find *its* default printer in the current workstation's set of defined printers, it will print to the default Windows printer and ignore the setting of SET("PRINTER", 3).

You also have to "ZAP" the printer info in the "Expr" field.

If you create a report with a particular printer this is what you may get:


DRIVER=winspool
DEVICE=Brother MFL Pro Printer
OUTPUT=LPT2:
ORIENTATION=0
PAPERSIZE=9
COPIES=1
DEFAULTSOURCE=7
PRINTQUALITY=600

Now if you use A4 and the client wants to print on Letter, the report prints on A4 irrespective.

What you need to do is zap "tag" and "tag2" completely and for "Expr"
keep only stuff you require - I keep only the orientation where 0 - portrait and 1 = landscape.

I have a form that i use just before a compile which allows me to select a directory and does the work for me in a few seconds as compared to hours if you have 100+ reports to fix.

Can email if you need and you can change to your needs.

Now the orientation is taken from the report and other settings like page length etc from the printer settings which is as it should be.

Hope this helps

Bernard