Report Broken

[Asellus]

When I create a report, it works very briefly, then stops functioning. There
is no error message. Once it breaks, it is listed in the Reports Tab window
but does not repond in any mode. When the database file is opened, the
Reports Tab is displayed (instead of the Tables tab). Database Repair does
not fix the problem.

In addition, during the brief time that the newly created report is still
functioning, it will not save the printer page settings. The page
orientation and margins switch every time I change mode or close and reopen
the report.

My default printer is HP "JetSuite Document Capture" (for a LaserJet) which
creates a print file to disk. (My printer is connected to another computer
and I must transfer the files for printing. There is no physical printer
connected to the computer on which Access is installed.) Changing the
default page settings in the "printer" does not prevent the loss of those
settings in Access.

I have run the Office Repair Tool, but it says my installation is fine.

This problem occurred in a simple flat (one table, one query) database.

Additionally, the on-line Help feature does not function, though there is
nothing wrong with my internet connection and I can access the MS sites just
fine. (This is probably a separate problem, but thought I'd mention it just
in case it is a clue.)

I have Access2003 SP2 OEM version (as part of Office Pro) with XP Media
Center. This is my first use of the program on the new computer. I have
much prior Access experience.

Needless to say, having non-functioning Reports renders Access fairly
useless. I eagerly await a solution.

 

[Allen Browne]

The symptoms suggest that either Access is confused by this printer driver,
or else there is a corruption within the database.

If it is the printer driver, you could solve the issue by installing another
printer under Windows Control Panel | Printers. (Note that you don't have to
buy another printer: just choose a completely different printer such as an
ink jet of a brand you are aware of.)

If it is a corrupted database, this sequence might help:

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, reference ambiguities are resolved,
and the code syntax is compilable.

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

 

[Asellus]

Thank you for your prompt response.

The "printer" is the source of confusion. If I set the Windows default to
the (non-existent) printer, Access is happy and the report functions. I can
still print to file by selecting the "document capture" device in the
File>Print command without creating any problems.

It is a nuisance to have to change the Windows default printer whenever I
use Access. But, at least it works.

I also ran through your other steps, though they made no difference. Still,
I removed the "name auto correct" and "ADO reference". Why invite trouble I
don't need? (I can handle field name changes myself, should I have such an
inclination.)

PS: Changing the default printer also resulted in the online Help working.
WEIRD!!

 

[Allen Browne]

Okay, here's a crazy idea.

Since you are using Access 2003, you could write a function that switches
the Printer for you whenever you start Access, and RunCode in your AutoExec
macro. This automatically solves the issue for you whenever you start
Access. (Of course you would need to reset the Printer before printing a
report.)