Link to home
Start Free TrialLog in
Avatar of LostInWindows
LostInWindowsFlag for Canada

asked on

Can I force user shares to close or logoff

Last night I thought I had logged everyone off their workstations – used my master key to access all but 2 offices. I determined everybody was logged off. Still I got a message that I did not have exclusive access to the Access database which usually means that someone is still logged on the database.

I am using SBS 2008. All workstations are either Vista or Win 7.

How can I have all computers log off after a certain period of inactivity? Or after a certain time of day? Or can I force all user shares to close?
ASKER CERTIFIED SOLUTION
Avatar of Scott McDaniel (EE MVE )
Scott McDaniel (EE MVE )
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of LostInWindows

ASKER

Is the .ldb file created on the workstation or on the server? If on the server, is it in the Database directory?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hmmm, sounds interesting. let me ask...
<Is the .ldb file created on the workstation or on the server? If on the server, is it in the Database directory? >

Assuming you're working with a split database architecture (a Backend consisting of Tables ONLY, and multiple FrontEnds consisting of everything else):

The .ldb file for the Backend will be in the same directory as the Backend, and it'll have the same name. For example, a file named MyBackend.mdb will produce a Lockfile name MyBackend.ldb.

The .ldb file for the Frontend will be on the user machine in the folder that holds the FE database (assuming you've deployed a COPY of the FE to each user). If you haven't deployed an FE to each users, then you'll need to search the target machines for .ldb files and attempt to delete them.
Hi LSM,
There is 1 database located on the server with everything in it. The database has a lot of links to picture files also located on the server.  
All users except for 3 'programmers' are using Access Runtime 2007.
<There is 1 database located on the server with everything in it. >

Then the .ldb file should be on the folder where that database is located. You might also consider rebooting the machine hosting the database, as this will remove all Windows locks on that file.

Further: The database should be split to a Backend and Frontend scenario, and you should deploy a copy of the FE to each user. While you may have been fortunate enough to have no issues so far, you'll eventually run into them - corruption, performance issues, record locking, etc etc.
Thanks for the great suggestions