Database corrupted - can't repair !?!

A user has reported a problem with an Access 2000 database. Upon open the database asks for a password and then says 'needs to be repaired or isnt a database file'. This database is protected by a password. When I say 'Yes' to repair, I get a message 'not a valid password' and then a message 'cant be repaired or isnt a database file'.
I cant get into the database at all to even import components to a fresh database.
What should I advise the user to do? I'm supposed to be the Access expert. This database is not split and apparently an update conflict occured - which led to this error. Is it a total loss? Is there anything else I can try?

Tell the user to make frequent backups of important files, or store it on a
LAN and make sure the LAN is backed up on a regular basis.

Did the database not contain a password before? Seems to me you could
repair it if the password were supplied.

I have heard that this can happen if someone tried to open an MDB file in
MSWord by mistake. The few times it happened to one of my users we had to
fall back to a backup copy.

Rick

"David" wrote in message
...
A user has reported a problem with an Access 2000 database. Upon open the
database asks for a password and then says 'needs to be repaired or isnt a
database file'. This database is protected by a password. When I say 'Yes'
to repair, I get a message 'not a valid password' and then a message 'cant
be repaired or isnt a database file'.
I cant get into the database at all to even import components to a fresh
database.
What should I advise the user to do? I'm supposed to be the Access expert.
This database is not split and apparently an update conflict occured - which
led to this error. Is it a total loss? Is there anything else I can try?

Sequence of events:
(1) Double click on .mdb
(2) Asks for password
(3) Correct password is entered
(4) Says 'repair' is needed
(5) repair requested
(6) Says 'not a valid password'
(7) Click on OK
(8) Says 'repair is needed'

Sounds like it might not be repairable. Hopefully one of the MVPs will have
more advice.

I once used a product called "jetcomp" that was able to repair a file that
was pretty badly corrupted. You might do a search and download jetcomp and
try it in the meantime.

Rick

"David" wrote in message
...
Sequence of events:
(1) Double click on .mdb
(2) Asks for password
(3) Correct password is entered
(4) Says 'repair' is needed
(5) repair requested
(6) Says 'not a valid password'
(7) Click on OK
(8) Says 'repair is needed'

Unfortunately, we are not allowed to download files, we can get fired for doing that!

If you are dealing with critical data you should be able to get your IT
department to either download the file for you or, else, give you special
permission to do so this time. Something else you might try is to create a
new blank database and import all the objects from the old database into the
new one. The import process may very well identify the offending object from
the original database.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


"david" wrote in message
news
Unfortunately, we are not allowed to download files, we can get fired for
doing that!

I tried importing to a new database but that did not work because it can't import from a corrupted database. I get prompted for the password and to repair the database just as if I was trying to open it.

Well, since Jetcomp was on Microsoft's site I risked being fired and downloaded it. It was able to recover the database. Thanks for the helpful information. I had never heard of that utility- very useful.

Since you used the tool to recover important data, then I'm sure you have a
good case if anyone ever questions you about it. I certainly hope you don't
get fired over something like that. I am glad you got it to work.

--
Lynn Trapp
MS Access MVP
www.ltcomputerdesigns.com
Access Security: www.ltcomputerdesigns.com/Security.htm


"David" wrote in message
...
Well, since Jetcomp was on Microsoft's site I risked being fired and
downloaded it. It was able to recover the database. Thanks for the helpful
information. I had never heard of that utility- very useful.