>>>>...
>>>>>...Prompt clause provides a way to set properties for the printer. Also you could do a trick to modify frx at runtime :
>>>>>

>>>>>lcFilename = "R"+sys(2015)
>>>>>copy file myreport.fr* to (lcFilename+".fr*")      && Myreport.frx in exe
>>>>>use (lcFilename+".frx")  * modify lcFilename.frx
>>>>>...
>>>>>use
>>>>>report form (lcFilename) ...
>>>>>erase (lcFilename+".fr*")
>>>>>

>>>>>Cetin
>>>>
>>>>Thank you for responding!
>>>>
>>>>I thought about your idea already. I may have to do that. The problem still exists, in that the user changes the printer parameters through the system dialog that comes up when I use PROMPT and I cannot figure out how to get feedback from that dialog. They can change the destination and paper tray but the report ignores the page orientation.
>>>I think you should play with FRX then. Try second way and then :
>>>

>>>*modify frx
>>>blank fields expr,tag,tag2  && Kill pdriver setup
>>>* Now try with ..printer prompt
>>>

>>>Cetin
>>
>>Thanks Cetin.
>
>Cetin,
>
>I have my doubts about this. In fact by opening the .frx, you are not changing the version that is used by the .app or .exe that resides within it. My guess (but I might be wrong) is that prompt overwrites some settiing at runtime only. It is possible to leave the report out of the build exe, but in multiuser systems I think this creqtes more problems than it solves.
>
>Marc

PMFJI, but what sort of problems have you experienced by leaving the report.frx out of the .exe? Curious users? "File not found", errors?

Thanks