Network shared database & want to identify users logged on to it

[Guest]

We have a large historical library database used by over 200 individuals to
store reference documents with hyperlinks to other documents. However,
individuals use the DB and stay on over great periods of time locking it from
the adminstrator being able to make changes. We would like to identify the
user(s) on the DB to send a note to get off when they stay on to long. We do
not limit access as we provide access to all users who can enter our server.
We are not very knowledgeable on SQL

 

[John Vinson]

We have a large historical library database used by over 200 individuals to
store reference documents with hyperlinks to other documents. However,
individuals use the DB and stay on over great periods of time locking it from
the adminstrator being able to make changes. We would like to identify the
user(s) on the DB to send a note to get off when they stay on to long. We do
not limit access as we provide access to all users who can enter our server.
We are not very knowledgeable on SQL

First off - SPLIT YOUR DATABASE!!! With 200 users it's absolutely
*essential* that each user (or each workstation at any rate) have a
separate "frontend" database, linked to a shared backend. This lets
the developer work on a new user interface, and provide the users with
the latest version when it's done. See

http://www.granite.ab.ca/access/splitapp/index.htm

for a thorough discussion.

Tony's site also has suggestions for frequent updates and other ideas
which you may find helpful.

John W. Vinson[MVP]

 

[Guest]

Hi JW,

See the topic titled "Close inactive sessions" in this article:

Implementing a Successful Multiuser Access/JET Application
http://www.access.qbuilt.com/html/multiuser_applications.html


Tom

http://www.access.qbuilt.com/html/expert_contributors.html
http://www.access.qbuilt.com/html/search.html
__________________________________________

:

We have a large historical library database used by over 200 individuals to
store reference documents with hyperlinks to other documents. However,
individuals use the DB and stay on over great periods of time locking it from
the adminstrator being able to make changes. We would like to identify the
user(s) on the DB to send a note to get off when they stay on to long. We do
not limit access as we provide access to all users who can enter our server.
We are not very knowledgeable on SQL

 

[Tony Toews]

We have a large historical library database used by over 200 individuals to
store reference documents with hyperlinks to other documents. However,
individuals use the DB and stay on over great periods of time locking it from
the adminstrator being able to make changes. We would like to identify the
user(s) on the DB to send a note to get off when they stay on to long. We do
not limit access as we provide access to all users who can enter our server.
We are not very knowledgeable on SQL

HOW TO: Detect User Idle Time or Inactivity in Access 2000 (Q210297)
http://support.microsoft.com/?kbid=210297
ACC: How to Detect User Idle Time or Inactivity (Q128814)
http://support.microsoft.com/?kbid=128814

However we found that the code which runs on the timer event must be
disabled for the programmers. Otherwise weird things start happening
when you're editing code.

Also print preview would sometimes not allow the users to run a menu
item to export the report to Excel or others. So you had to right
click on the Previewed report to get some type of internal focus back
on the report so they could then export it. This was also helped by
extending the timer to five minutes.

The downside to extending the timer to five minutes was if a person
stays in the same form and at the same control for considerable parts
of the day, ie someone doing the same inquiries, the routine didn't
realize that they had actually done something. I'll be putting in
some logic sometime to reset this timer whenever they do something in
the program.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm

 

[aaron.kempf]

1) use sql server or msde instead of mdb if you care about your data at
all
2) use sp_who2 in order to see who has connections
3) rinse and repeat