I believe the global option to "Save printer environment" affects new reports only. Existing reports will carry on whatever option they where saved with. There's also a bug in Report Designer. Printer Environment becomes enabled if you change Font on any object using Righ-click, Properties, Stye Tab, Fonts. I don't think modifying report in any other way will enable Printer Environment

>Some earlier versions of VFP always save the printer environment when reports are saved. This causes reports developed in one environment to not always run properly in a different environment where printers are different. This is an issue when distributing reports; one has to manually open the .FRX as a table, go to the first row, and delete unnecessary cruft from the .Expr, .Tag and .Tag2 columns.
>
>VFP9 (and maybe earlier versions too, haven't checked) recognizes this issue. In Tools...Options...Reports tab, there is a global option to "Save printer environment", which by default is disabled. So far so good.
>
>However, if:
>
>- You are given a report .FRX/.FRT where the printer environment has been saved (whether in VFP9 or some earlier version)
>- The printer stored in the report is NOT present in your environment
>- You modify and save the report
>
>Then, YOUR default printer information/environment is saved with the report, even though the global save option is disabled.
>
>When you send the report back, the user complains it doesn't print properly any more.
>
>That's behaviour that was new for me - maybe this message will save someone else some head-scratching.