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

Unable to open Backend Database

P: 3
Hello,
I am in charge of maintaining a little ACCESS database used by our purchasing department. I need to add some new values to a table, but I can't open the .be database in order to access the table involved.

Not really understanding what is keeping me out, I have investigated a .ldb database, which I believe is a locks database. I can open this with textpad and, even when all users are logged out of the application, there is one machine name still in the table. I corresponds to 3 people, who I cannot believe were logged into this database at 7:50 a.m. They are all systems people, including one who is the domain administrator (the database is location on a network drive).

Does anyone have any suggestions as to whether this locks file is keeping me from accessing the backend tables, or have another idea about why I can't open the backend tables. I can click on the file name in the directory, get the message about opening even with macros, and then nothing. the fetch hourglass disappears, but the ACCESS window remains empty.

Many thanks.
Susan
University of New Orleans
Sep 7 '06 #1
Share this Question
Share on Google+
7 Replies


PEB
Expert 100+
P: 1,418
PEB
Hi,

try to delete the ldb file!

When all users are out of the database try to enter!

Is ther any special messages that appear when you try to enter?
Sep 7 '06 #2

P: 3
Do you think that the locks file is keeping me from viewing and working on the tables in the backend database?
Thanks,
Susan
Sep 7 '06 #3

MMcCarthy
Expert Mod 10K+
P: 14,534
The appearance of the ldb file simply means that the database has been opened by a user. If that user opened it exclusively you still should be able to access it as read only. However, I agree with PEB just delete this file if possible.

You may find you won't be allowed to delete it and will have to find the user who has the system open. If the ldb was left there by an incomplete shutdown I would suggest trying any of the users who were likely to have it opened to see if they can shut it down.

Do you think that the locks file is keeping me from viewing and working on the tables in the backend database?
Thanks,
Susan
Sep 7 '06 #4

PEB
Expert 100+
P: 1,418
PEB
If you can't delete the ldb ffi you can do Copy Paste to the mdb file to an other folder and try to open your database from there!

:)
Sep 8 '06 #5

P: 3
Thanks. Yes, I did copy only the mdb to a separate work folder. Apparently, the locks file is NOT the issue keeping me from accessing the tables in the backend database. I know this for sure now because I got into work early enough and got the users to cooperate so that I was able to copy the be and the mdb before anyone had opened the application (no locks file).

So... I'm wondering where I might look to see if and what other security might be in place. Any ideas?

many thanks.
Susan
Sep 8 '06 #6

PEB
Expert 100+
P: 1,418
PEB
When you try to enter into the database when yous choose the mdb file please press the left shift key...

Is there any message that appears when you try to enter and what happens after?
Sep 8 '06 #7

PEB
Expert 100+
P: 1,418
PEB
If thhose things don't work in the net there was a VB code in case of those desasters... You can search in google MS Access code damage

If you don't find something so I'l send you this code! I've never tried!
Sep 9 '06 #8

Post your reply

Sign in to post your reply or Sign up for a free account.