secured.mdw corrupted

[Guest]

When entering a secured DB this morning, (Access 2003, mdb) the user received
the error:

"The Microsoft Jet database engine stopped the process because you and
another user are attempting to change the same data at the same time."

This appeared before even getting the login dialogue box. I've searched
for backup copies of the secured.mdw file but so far it looks like I didn't
think that far ahead.

Please help!

 

[Sylvain Lafontaine]

First, you should try to delete any associated LDB file.

 

[Guest]

Even when the problem started there wasn't any LBD files for either the mdw
or the mdb.

 

[Jeff Conrad]

Is that the only person receiving the error, or is
everyone else seeing the same problem?

--
Jeff Conrad
Access Junkie - MVP
http://home.bendbroadband.com/conradsystems/accessjunkie.html
http://www.access.qbuilt.com/html/articles.html

in message:

 

[TC]

There will /always/ be an ldb file for the database /and/ the workgroup
file (ie. two ldb files) unless, I think, you start Access with the
/excl and /ro switches.

If you don't have a backup copy of the workgroup file, you should at
least have written down the information that you used to create it.
Then you can recreate it by using the same information.

HTH,
TC

 

[Guest]

There will /always/ be an ldb file for the database /and/ the workgroup
file (ie. two ldb files) unless, I think, you start Access with the
/excl and /ro switches.

If you don't have a backup copy of the workgroup file, you should at
least have written down the information that you used to create it.
Then you can recreate it by using the same information.

HTH,
TC

The ldb file is only created when a user gains access to the database, where
there is a secured db the secured.mdw and the main db.mdb both would create
an ldb file. But in this case, no one is gaining access to either file so no
ldb file is created.

 

[Guest]

Everyone who tries to open the database gets the same error message. I've
tried over-writing the secured.mdw file with one from another database, (the
database I stole the mdw file from has most of the same users including
myself as the administrator), but apparently it matters because although it
presents me with a log-on dialogue box, it will not recognize my user name.
(just thought that might do the trick)

 

[robert d via AccessMonster.com]

Bill:

I've had problems with database corruption, but not exactly like yours. I
haven't taken the time to thoroughly understand your problem, so maybe this
won't help you at all (but it may help others).

When my application, which is written in Access 2002 (default file format of
Access 2000), opens and the corruption message is displayed, I don't panic
anymore. I just go to my laptop and open the app (I have a home network) in
Access 2000. Every single time, it has opened successfully in Access 2000
and thereafter opens successfully in 2002.

Don't know if this will help, but if all else fails...

Everyone who tries to open the database gets the same error message. I've
tried over-writing the secured.mdw file with one from another database, (the
database I stole the mdw file from has most of the same users including
myself as the administrator), but apparently it matters because although it
presents me with a log-on dialogue box, it will not recognize my user name.
(just thought that might do the trick)

Is that the only person receiving the error, or is
everyone else seeing the same problem?

[quoted text clipped - 8 lines]