By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,956 Members | 1,722 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,956 IT Pros & Developers. It's quick & easy.

MS Acces help needed

P: n/a

Someone knows how to drop this big difficulty??

A Data Base in MS-Access 2002, condivided with multiple client, had link
failure with a client.
From this time until now, none can open the file because it appear following
message (translation from italian):

<<Microsoft Jet Manager stops working because another client want to modify
same data.>>

If I don't find how to overcome this problem and I can open again the file,
I loose part of my Data Base.
This is a big damage for me and it is not a good advertising for Microsoft
packages.

Can I open with other Data Base or Packages the file and repair it?
Which is the best?

Thank You very much

Alberto

Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
jv
Is the .ldb file still exist even though no one is in the database?
This happens to us once in a while when a network error occur. We
would get a message saying that the database is read-only. If that is
the case then try the following:
-Close all connections to this database.
-From the a Windows server machine, click on Start, Run, then type
in srvmgr,
then Click OK. This should open the Server Manager utility with a
list of computers
on the network.
-Double click on the server name where the data resides.
-Click on In Use. Another window will appear showing you a list of
open resources.
-Look in the Path column for the name of your database. If you see
any open resource
for the database, then highlight the line and click on Close
Resource until all
resources for that database is closed.
-Open windows explorer and see if the .ldb still exist. It it still
exist,
try to delete it.
-Try to open your database to see if the problem is solved.

If the above does not take of the problem then make a copy fo the
database and try the following on it:
-Repair and Compact, if you are able to get to it.
-Download JetComp.exe and try repairing it using the utilities.
-Decompile the database from the command promp using the the
/decompile switch.
-Import the data and objects into another database.

Good Luck

Julie Vazquez

Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.