"Housten we have a problem" (Could not use 'Database_be.mdb';File already in use.)

[Groundrush]

"Housten we have a problem" (Could not use 'Database_be.mdb';File already in use.)

We have been having Problems with our server over the past few days, and this morning we had to shut it down.

Since then we have not been able to gain Access to our Databases (no pun intended).

Even though no one has the database open, is tells you that the file is already in use.

We shut it down the second time and it let us in, but when a user tried to enter some data it refused to update the records and left a message that another user has made changes and cant save the changes.

Since then no one has been able to get into the database, now it has effected 2 databases on the network, both are split with the front & back end on the server, but users use a copy of the front end on their hard drives.

Does anyone have any ideas, as our IT Dept does not seem to know.

Any help would be greatly appreciated

thanks

 

[The_Doc_Man]

Sounds like a lock problem.

First thing to consider: With no one in the database, is there still a {database-name}.LDB file in the same directory? If so, kill it. Delete it. Beat on it until it is dead. Get your network admin person's help if it resists.

Second thing to consider: You don't say which kind of network you have, but all sharing systems have SOME sort of lock system. If the .LDB issue doesn't pan out, ask your network admin if there is a lock management utility that could be used to unlock the database.

Third thing to consider: If this used to work and now doesn't, you might ask the network admin to verify that the rights on the database have not somehow been changed. Ditto the directory.

Remember, in order to use a shared database, you need certain rights on that shared directory.

You need the right to create, delete, modify, scan for, and read files. Without these rights, you cannot properly manipulate the .LDB file. And a hosed-up .LDB file is the first thing I look for when you get the message you reported.

 

[donbettis]

My first actions toward this problem would be the same as The_Doc_Man’s. The next thing I would consider is that the Database_be.mdb may be opened exclusively. If the database has been opened exclusively it will give the same error.

Don

 

[Groundrush]

Thanks, I knew I would get a better answer from this Forum than from our "IT Dpt"

I think its got something to do with the rights on the network as suggested

hopefully will find out soon.

thanks