Problem with portrait/landscape in page setup.

[Rob Parker]

Definitely not a newbie, but this one's got me really scratching my head ...

Using A2003 (.mdb file in A2000/2002 format - slightly different problems
with A2003 and A2000):

I have a report which uses the default printer, and its page set-up is set
to landscape. The report is opened via a command button in preview mode.
Differing problems on different computers:

1. Computer with A2003: report opens in landscape format in preview mode,
but when Print button is clicked report prints in portrait mode.

2. Computer with A2000: report opens in portrait format in preview mode;
opening Page Setup shows that Landscape format is selected, clicking OK to
exit the Page Setup dialog causes report (in preview mode) to be (correctly)
formatted in Landscape mode; subsequently prints correctly.

The computer have different default printers, so I don't think it's related
to the printer driver itself.

Any thoughts/suggestions gratefully received,

Rob

 

[strive4peace]

Hi Rob,

When you put the database into another environment, open
each report in design view, check the settings, and save it
in design view.

There may be a better way, but this is what I have had to do
in the past in certain environments with landscape reports
or reports that use Legal paper instead of Letter. As I
figure, it is not the printer driver, it is that the default
printer is different than the one used to design the report.

You might try using code to do this and see if that works...



Warm Regards,
Crystal
Microsoft Access MVP 2006

*
Have an awesome day

remote programming and training
strive4peace2006 at yahoo.com

*

 

[Rob Parker]

Hi Crystal,

Thanks for the comments. I'm actually developing on a computer on a
network, and the end-user is using it on a separate network, so during the
development/testing the same .mdb file is getting copied from one machine to
another via a memory stick (high-tech "sneaker net"). And the report might
well get opened (in design mode) and saved on different computers as part of
this process. This could explain why the problem occurs on the
computer/printer on which the report was originally designed.

If that's the case, the problem might well go away when the development ends
and the application is running only on a single machine (it is not designed
or required to be a multi-user app). It does have a form which allows the
user to select a different printer as the default printer (while the app is
running - it resets to the previous default when the app closes), since
there is a need to swap between a real printer and a .pdf printer for the
same report. Hopefully that won't cause the problem to keep recurring.

Again, thanks,

Rob

 

[strive4peace]

you're welcome, Rob happy to help

Warm Regards,
Crystal
Microsoft Access MVP 2006

*
Have an awesome day

remote programming and training
strive4peace2006 at yahoo.com

*