Reports Revert from Landscape back to Portrait (Office 2003)

[jason.gyetko]

I see all kinds of posts out here for a bug in Office 2000 that makes
the reports revert back to portrait from landscape. I'm having the
same problem with Office 2003. I was runnning Windows 2000 Pro and
Office 2000 just fine, I recently upgraded from Office 2000 to Office
2003 and now am experiencing this problem with the reports. If I
change the report to landscape, it will not save. I have to change it
everytime I open it. Any suggestions would be appreciated. Thanks.

MS Office Access 2003 (11.6566.6568) SP2
Ms Windows 2000 Professional Version 5.0.2195 SP 3 Build 2195

 

[Allen Browne]

Firstly, check that you are using a paper size that is supported by your
printer. If you change printer (or computer) to one where the paper size is
different, all bets are off.

If that is not a factor, then it sounds like you have a corruption affecting
this report. To rescue it:

1. Uncheck the boxes under:
Tools | Options | General | Name AutoCorrect
Explanation of why:
http://allenbrowne.com/bug-03.html

2. Compact the database to get rid of this junk:
Tools | Database Utilities | Compact

3. Close Access. Make a backup copy of the file. Decompile the database by
entering something like this at the command prompt while Access is not
running. It is all one line, and include the quotes:
"c:\Program Files\Microsoft office\office\msaccess.exe" /decompile
"c:\MyPath\MyDatabase.mdb"

4. Open Access, and compact again.

5. Open a code window.
Choose References from the Tools menu.
Uncheck any references you do not need.
For a list of the ones you typically need in your version of Access, see:
http://allenbrowne.com/ser-38.html

6. Still in the code window, choose Compile from the Debug menu.
Fix any errors, and repeat until it compiles okay.

At this point, you should have a database where the name-autocorrect errors
are gone, the indexes are repaired, inconsistencies between the text- and
compiled-versions of the code are fixed, and reference ambiguities are
resolved.

If it is still a problem, the next step would be to get Access to rebuild
the database for you. Follow the steps for the first symptom in this
article:
Recovering from Corruption
at:
http://allenbrowne.com/ser-47.html

Another alternative would be to export this report to a text file, using a
command such as this:
SaveAsText acReport, "Report1", "C:\Report1.txt"
Delete the report.
Compact the database.
Then import it from the text file:
LoadFromText acReport, "Report1", "C:\Report1.txt"