Page Setup Orientation is changing on me

[Seth Schwarm]

Access XP

Access 2000 format

I have an application I have written and made 5 updates
to over the last year.

Two weeks ago I made an update to the front end and
something odd happened that I haven't experienced
before. The orientation of my reports have flopped to
landscape from portrait. I have 30 reports, but only
three have done this.

I went into their design view, then page setup, then
orientation and set it back to portrait. Then I saved
the report. The next time I opened the report it was
back to landscape orientation.

In previous updates I made my modifications using Access
2000, this time I made my modifications using Access XP.
This is the only thing that has changed.

What is up with this?

Thanks,

Seth

 

[Guest]

I have similar problem when exporting to snapshot, which
is automated by code. It works fine in about 7 databases
but has changed inside 2 databases. The snapshot file is
now saving in these 2 databases in a smaller view and not
proportionate to the report. I have the most current
viewer (Snapview.exe), but it still does not allow me to
right-click and get larger magnified view. The report
looks fine, and I can print from there. However, rather
than have to scan in the reports to send to people, I
wanted to have the snapshot file saved on hard disk--just
as I do in the other 7 databases. (I am working on
Windows 98 with Access 2000, Version 9.)

Please help, as I use snapshot files to include as
invoice attachments to be e-mailed.

Do I need to include somewhere in the code something
about waiting (does this have to do with warnings, echo,
or what?) x amount of time before running other code?

My other 7 databases are still working correctly; I am
afraid something will happen to them as well, since I
execute code when the report is activating; however, I do
not have code executing on close on the 7 as I do on
these 2.

Thanks.

 

[Aloysius]

I am experiencing the same problem.
I have an Access 2000 database (originally in 97, converted to 2000).
have several reports that contain multiple sub reports. Th
page-orientation on each of them is set to Landscape.
However, when you open the report, it appears in Portrait. If you chec
page setup, it IS set to landscape.
If you close the report and then reopen -poof, it's in landscape jus
as it should be.
Opening the report in design view and resaving the landscape settin
has no effect.

Any help is greatly appreciated!

(And yes, I have Track name Autocorrect turned OFF!
I have also started with a BLANK database and created a BRAND NE
report. If you use the Wizard to create a landscape report all run
smooth. However, as soon as you make ANY change to the page setu
(modify margins) and then save the report, this error start
happening...)


My temporary work around is an AutoExec macro that opens a report i
preview mode and then immediatly closes it. Cheesy, but it works.

I have another database in which SOMETHING in my open process (lauche
a form, runs some code) must also act as a workaround, but I've yet t
track down exactly WHAT!!

 

[Aloysius]

I am experiencing the same problem.
I have an Access 2000 database (originally in 97, converted to 2000).
have several reports that contain multiple sub reports. Th
page-orientation on each of them is set to Landscape.
However, when you open the report, it appears in Portrait. If you chec
page setup, it IS set to landscape.
If you close the report and then reopen -poof, it's in landscape jus
as it should be.
Opening the report in design view and resaving the landscape settin
has no effect.

Any help is greatly appreciated!

(And yes, I have Track name Autocorrect turned OFF!
I have also started with a BLANK database and created a BRAND NE
report. If you use the Wizard to create a landscape report all run
smooth. However, as soon as you make ANY change to the page setu
(modify margins) and then save the report, this error start
happening...)


My temporary work around is an AutoExec macro that opens a report i
preview mode and then immediatly closes it. Cheesy, but it works.

I have another database in which SOMETHING in my open process (lauche
a form, runs some code) must also act as a workaround, but I've yet t
track down exactly WHAT!!