My Access table is exclusively in use, how do I fix?

[Guest]

My manager wanted a way around splitting the database (for a multi user
environment), so I attempted to put the whole thing on a shared folder. The
database was in bak. file form from a previous screwup. So I went to convert
it to an mde. so it was recognized when the users tried to pull it up. Now I
am getting a message saying that my main table is exclusively in use and my
macros that require that table are not working. HELP!!!!!! P.S I am a first
time access user, so please be patient. Thanks!

 

[John Vinson]

My manager wanted a way around splitting the database (for a multi user
environment), so I attempted to put the whole thing on a shared folder.

The manager wants to AVOID using the standard, preferred technique,
and instead wants to use a technique pretty much guaranteed to cause
bad performance, increase the risk of corruption, and risk losing the
entire database?! WHY? ***Split the database***.

The database was in bak. file form from a previous screwup. So I went to convert
it to an mde. so it was recognized when the users tried to pull it up. Now I
am getting a message saying that my main table is exclusively in use and my
macros that require that table are not working. HELP!!!!!! P.S I am a first
time access user, so please be patient. Thanks!

You need to, first, get around this idea that you can put "the whole
thing on a shared folder". Well, you *CAN*, but with the major
disadvantages noted above.

Secondly, you MUST - NO OPTION - have a working .mdb file. A .mde file
does not allow ANY design changes to code, forms, reports, etc.

Thirdly, renaming the extension from .bak to .mde to .mdb does nothing
whatsoever to change the structure or format of the file. I'm hoping
that you've been very, very lucky and that the .bak file was the
backup of your master .mdb file. Try renaming it to .mdb (just to ease
confusion), delete any file with a .ldb extension in the same folder,
and try opening it again.

You may want to read the advice at Tony Toews' excellent site

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

for suggestions about how to prevent and recover from database
corruption. His website also has a good discussion of the advantages
of splitting.

John W. Vinson[MVP]

 

[Joseph Meehan]

The manager wants to AVOID using the standard, preferred technique,
and instead wants to use a technique pretty much guaranteed to cause
bad performance, increase the risk of corruption, and risk losing the
entire database?! WHY? ***Split the database***.
...

John W. Vinson[MVP]

I want to add my support to John's comments. Splitting a database is
done, not to complex the process but to make sure it works with fewer
problems and faster. Consider trying to encourage the manager to allow it
to be split.