mdb looks and acts like mde

[Monish]

Hi

I have a FE split mdb file, which seems to have been corrupted.

The FE mdb does not open due to error stated as "The Microsoft Jet database
engine stopped the process because you and another user are attempting to
change the same data at the same time"

There is a mde file which shows the (locked) icon - but i cannto see any
..ldb file anywhere. This mde file opens fine.

There is another mdb file, which only opens looking and acting like an mde
file (with no Design views)

Does anyone have any ideas on how I might recover my mdb file?

Thanks!

 

[Jerry Whittle]

The first thing to do is to make a complete backup of all the files involved
and put them away somewhere safe.

The second thing to do is to look for your most recent backup files. As it's
the FE causing problems, you shouldn't lose any data replacing it.

You should also check the shortcut, assuming that you are using one, to the
problem database file just to make sure it's actually hitting the mdb file
and not a mde.

Another thing to check are your privileges to the files and folder holding
the database files. Make sure that you have Read, Write, Create, and Delete
privs to them.

Assuming that you may have a corrupt database:

Tony Toews has an excellent web page on database corruption.
Http://www.granite.ab.ca/access/corruptmdbs.htm

Allen Brown also has excellent info on corruption.
Http://allenbrowne.com/ser-47.html

I have a white paper in a Word document named Fix Corrupt Access Database.
Click on "Whittle, Jerry" on this page:
http://www.rogersaccesslibrary.com/forum/default.asp?C=1

 

[Arvin Meyer [MVP]]

One of the older tricks when MDE's first came on the scene was to rename
them as MDBs. Sometimes MDB files really are MDE's. To find out, you can
simply change the extension to MDE and see if it opens that way.

If the file is corrupted, take the following actions:

First, always work on a copy of the database. Working on the original may
make it impossible for a repair service to fix it.

Decompile your database:
http://www.trigeminal.com/usenet/usenet004.asp

Download a copy of JetComp.exe:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;273956

Try backing up your forms as text with the undocumented SaveAsText
LoadFromText functions:

http://www.datastrat.com/Code/DocDatabase.txt

Also have a look at the Microsoft KB article:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;209137

Then have a look at Tony Toews' Access Corruption FAQ at:

http://www.granite.ab.ca/access/corruptmdbs.htm

for some suggestions. Unfortunately, some corruption cannot be fixed - you
may need to create a new database, import what can be salvaged, and recreate
the rest.

Although it's a paid service, Peter Miller does an outstanding job of saving
corrupt databases. Try this URL:

http://www.pksolutions.com

 

[David W. Fenton]

One of the older tricks when MDE's first came on the scene was to
rename them as MDBs. Sometimes MDB files really are MDE's. To find
out, you can simply change the extension to MDE and see if it
opens that way.

Or, check the database's MDE property:

?CurrentDB.Properties("MDE")

If it's an MDE, that will return "T".

If it's not, it will return an error (because the property doesn't
exist).