Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Report Orientation Changes
Message
General information
Forum:
Visual FoxPro
Category:
Reports & Report designer
Environment versions
Visual FoxPro:
VFP 9
OS:
Windows XP SP2
Network:
Windows 2003 Server
Database:
MS SQL Server
Miscellaneous
Thread ID:
01294012
Message ID:
01294192
Views:
21
You should NEVER have to install the driver of the printer that you use for development on the client's machine. That ***SCREAMS*** that the printer information is stored in the FRX.

Double check the TAG and TAG2 fields in the first record of the FRX to be sure they are empty. Then double check the EXPR field to be sure any printer-specific lines, such as DEVICE=, is not there. However, you do want to keep the lines such as ORIENTATION= to preserve the landscape definition.

Also double check the printer the user uses to see what the default settings are.

Also consider reinstalling the printer driver for the printer they use.


>I have several reports where this has happened and the scenario is as follows:
>
>The reports are supposed to print in landscape and were printing correctly when for no apparent reason they started to print in portrait. A new version of the application had not been installed and yet they started to print in portrait. When I printed the reports using the same production version of the application they printed correctly.
>
>While trouble shooting the reports on the users computers I determined that if I installed the printer that I used to develop and test the reports, the reports start printing correctly even though the user does not print to the newly installed printer. This would be alright, but when the report comes up this printer I justed installed comes up as the default printer and they print to it which is two floors down from where they sit and thus they just print it again.
>
>I never save the printer environment in my reports and have even gone into the report's tables to strip out any printer specific information but that hasn't helped. Has anyone run into a similar situation out there?
Cathy Pountney, Microsoft Visual FoxPro MVP
Memorial Business Systems, Inc. (www.mbs-intl.com)

My Website: (www.frontier2000.com)
My Blog: (www.cathypountney.blogspot.com)
My Book: The Visual FoxPro Report Writer - Pushing it to the Limit and Beyond
Free MSDN Article: What's New in the VFP 9.0 Report Writer
Free MSDN Article: The VFP 9.0 Report Writer In Action
Previous
Reply
Map
View

Click here to load this message in the networking platform