Wrox Home  
Search P2P Archive for: Go

  Return to Index  

access thread: DB loacked by Admin


Message #1 by "Kenny Alligood" <kennyalligood@h...> on Thu, 29 Aug 2002 02:18:52
I have a DB that is used in a multiuser environment and was designed 
without UserLevel Security (I created my own username and password forms 
and code). The DB was designed in Access 2K and is used in WinNT, Win2K, 
and WinXP OS. 

The problem is that I periodically get the message that the DB is opened 
by Admin on a particular set and therefore can not be opened again. I 
don't understand why this is happening because there is only 1 person (me) 
that has Admin access and so far the solution to correct this problem is 
to delete the DB from it's current folder and copy a fresh DB back into 
the folder. 

What I would like to find is a solution that will stop this situation from 
happening at all. If anyone has any ideas I would sure appreciate the 
input.

Thanx
Kenny
Message #2 by "Haslett, Andrew" <andrew.haslett@i...> on Thu, 29 Aug 2002 13:15:33 +0930
Admin is the default user if you are not using Access Security. So its
basically saying that one of your other users has locked a certain record
and you can't access it.

This can be due to the locking settings you have on your form, tables or
even due to a corrupted copy of the database.

Also, a quick tip - check your processes in Task Manager and see if there
are two instances of MSACCESS.EXE running. This can often cause locking.

Cheers,
Andrew

-----Original Message-----
From: Kenny Alligood [mailto:kennyalligood@h...]
Sent: Thursday, 29 August 2002 11:49 AM
To: Access
Subject: [access] DB loacked by Admin


I have a DB that is used in a multiuser environment and was designed 
without UserLevel Security (I created my own username and password forms 
and code). The DB was designed in Access 2K and is used in WinNT, Win2K, 
and WinXP OS. 

The problem is that I periodically get the message that the DB is opened 
by Admin on a particular set and therefore can not be opened again. I 
don't understand why this is happening because there is only 1 person (me) 
that has Admin access and so far the solution to correct this problem is 
to delete the DB from it's current folder and copy a fresh DB back into 
the folder. 

What I would like to find is a solution that will stop this situation from 
happening at all. If anyone has any ideas I would sure appreciate the 
input.

Thanx
Kenny
Message #3 by "George Oro" <george@c...> on Thu, 29 Aug 2002 09:49:43 +0400
Create your own Workgroup Information file and define all your users and user rights and joined them all
or see help file for more
info.


HTH
george
\^_^/


-----Original Message-----
From: Kenny Alligood [mailto:kennyalligood@h...]
Sent: Thursday, August 29, 2002 2:19 AM
To: Access
Subject: [access] DB loacked by Admin


I have a DB that is used in a multiuser environment and was designed
without UserLevel Security (I created my own username and password forms
and code). The DB was designed in Access 2K and is used in WinNT, Win2K,
and WinXP OS.

The problem is that I periodically get the message that the DB is opened
by Admin on a particular set and therefore can not be opened again. I
don't understand why this is happening because there is only 1 person (me)
that has Admin access and so far the solution to correct this problem is
to delete the DB from it's current folder and copy a fresh DB back into
the folder.

What I would like to find is a solution that will stop this situation from
happening at all. If anyone has any ideas I would sure appreciate the
input.

Thanx
Kenny

Message #4 by "Steven White" <Steve.White@m...> on Sat, 31 Aug 2002 11:31:20
Another thing you might want to check out is whether the default setting for Access is to open 
files in exclusive mode
Tools-->Options

You'd be wanting it to be opening in Shared by default, otherwise no one else will be able to 
open the file and you'll get the messages that I think yr getting - like
"Cannot access file - File Currently locked by user Admin on machine 0123489"

But I also agree that setting up yr own workgroup file is a good idea, and not let the user 
Admin have read access to all the MSys tables

This way, a user won't be able to open the file unless they have joined the workgroup.

  Return to Index