Open Exclusively

  • Thread starter Thread starter Troy Ward
  • Start date Start date
T

Troy Ward

Hello everyone,
I have a shared database on a server. Apprently the
database have become damaged and asks me to repair it.
When I hit ok to repair, it tries to open it exclusively,
but says that it can't be repaired because other user (me
on the same workstation im working on) is already logged
on exclusively. Any ideas?

Thanks,

Troy
 
Troy Ward said:
Hello everyone,
I have a shared database on a server. Apprently the
database have become damaged and asks me to repair it.
When I hit ok to repair, it tries to open it exclusively,
but says that it can't be repaired because other user (me
on the same workstation im working on) is already logged
on exclusively. Any ideas?
Click to expand...

The LDB file that would ordinarily be deleted automatically when the last user leaves
the MDB will in some circumstances not be deleted. If you delete that yourself
manually, then your problem should go away. Unless of course someone else actually
is in the file. That message is notorious for reporting the wrong user name. It can
only be relied upon to indicate that "someone" is in the file.
 
Ok i tried to delete the file but it gives me an error
saying that there is a sharing violation and that the file
may be in use.

Troy
-----Original Message-----


The LDB file that would ordinarily be deleted
Click to expand...
automatically when the last user leaves
 
Troy Ward said:
Ok i tried to delete the file but it gives me an error
saying that there is a sharing violation and that the file
may be in use.
Click to expand...

Whenever I have had that problem it was because someone else was actually in there.
If you open the LDB with Notepad it will list the computer names of people who were
in the file since its creation. Check with all of those workstations to make sure
that they are definitely out of your application.
 
Thanks. Your right one other person was logged on that I
couldnt find. Found him, logged it off. Deleted the file
and repaired it.

Troy
-----Original Message-----


Whenever I have had that problem it was because someone else was actually in there.
If you open the LDB with Notepad it will list the
Click to expand...
computer names of people who were
 
Back
Top