reports don't open in access 2003 after converting from Access 97

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I just converted an Access 97 database to Access 2000. Everyrthing works fine
when opening with Access 2000.

When opening with Access 2003 I can not print, preview or go into design
view of any reports.

I am signed onto the database as an Admin so I have rights to all objects.

Any help would be appreciated,

Thanks

Darren Lloyd
 
In A2003, press Ctrl+G to open the Immediate window.
Enter:
? Printers.Count
or try:
? Printer.DeviceName

I'm guessing that A2003 is unable to discover any printer. If so, it will
not be able to use the printer metrics to determine how to
create/interpret/view the report.
 
I get a count of four printers and a device name for my default printer.

Any other ideas?

Thanks for the response.
 
If Access is recognising the printers, the next suggestions would be:
a) There is some kind of corruption in the database (mdb).
b) There is a fault with the Office installation.
c) There are inadequate priviliges.

Are you logged in as a local computer administrator, or as a limited user?

I would expect some kind of error message if there is a problem with the
office installation (such as the wizards.)

If the database is corrupt, 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, 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
 
OK Allen I was able to do some more testing this weekend.

Here is what I found:

Access 2003 works on 10 other P.C.'s The users sign on to a domain and are
not Admins on the domain or P.C. If I sign on to the P.C. that is not
currently working with any other user name Access 2003 works fine.

So I have narrowed it down to the one P.C. and on that P.C. one user name.
Here is where it gets confusing, if I sign on as this user to another machine
everything works fine.

So in conclusion I have one P.C. that does not work with one user name, but
this user anme works on other P.C.'s

Any thoughts on this?

Let me know if this is not clear to you.

and thanks again for your time,

Darren Lloyd
 
Just to be clear, by "user" you are talking about the user-name you log into
the domain with (i.e. the Windows user name), not the user-name you log into
Access with (i.e. JET security model.)

If so, it would seem that this particular user has inadequate priviliges
somewhere, or something is broken with the machine. Darren, I don't know
what to suggest, so hopefully someone else will jump in.
 
Back
Top