Can't convert Access 2000 file to Access 2007 file.

E

eacantdraft

I recently upgraded from Access 2003 to Access 2007. I am having
trouble converting a file to the new 2007 format.

I get the following message "You attempted to open a database that is
already opened exclusively by user "Admin" on machine '(my profile)'.
Try again when database is available."

I am using Window XP Media Center 2005. I only have one user account
on my computer and no one else uses it. I'm not on any network. Does
anyone have any idea what the problems would be?
 
A

Allen Browne

Open the folder where the database is.
Is there a small LDB file with the same name in the same folder?
If so, delete it. (This file contains locking info. It is normally deleted
on exit, but may be left over after a crash.)

If that doesn't solve the problem, try holding down the Shift key while
opening the database. This should stop any startup code executing. You may
then be able to compact the database (Office Button | Manage.)

If you can't open it at all in A2007, but can in A2003, then try decompiling
the database using A2003. Try this sequence (in order):

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/Repair

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 (holding down the Shift key if you have any startup code),
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
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top