.ldb and idle users

[Guest]

My scenerio
Although a file-server solution can support up to 255 simultaneous users, if the users of our solution are frequently adding data and updating data, it is a good idea for an Access file-server solution to support no more than 25 to 50 users
Maintaining a database on a file server is inherently less reliable than using a database server such as SQL Server, because the database file can become damaged or left in an inconsistent state if the user's workstation, the network connection, or the file server fails while data is being written.

Therefore my dilemma is
As of now, I can't find a way to modify the .ldb file to kick off idle users after 30 minutes. Is this possible? There is way to run a module program to find out who and how many users have the database open.

 

[Joan Wild]

Here's one solution
http://www.datastrat.com/Download2.html - look for KickEmOff2K


--
Joan Wild
Microsoft Access MVP

My scenerio:
Although a file-server solution can support up to 255 simultaneous users,

if the users of our solution are frequently adding data and updating data,
it is a good idea for an Access file-server solution to support no more than
25 to 50 users.

Maintaining a database on a file server is inherently less reliable than

using a database server such as SQL Server, because the database file can
become damaged or left in an inconsistent state if the user's workstation,
the network connection, or the file server fails while data is being
written.

Therefore my dilemma is:
As of now, I can't find a way to modify the .ldb file to kick off idle

users after 30 minutes. Is this possible? There is way to run a module
program to find out who and how many users have the database open.