Access.lockfile.9

[Michelle]

I have an Access 2000 database with no roles or security
passwords. The database is split and many people have
access to the front end which resides on a shared server.
So, users are not using a copy of the front end, they are
all accessing the same copy.

Without going to the trouble of creating individual user
accounts, is there anyway I can capture the network login
of anyone who has the front end open?
OR
Is there any way I can boot off all users? Some users are
leaving the application open on their machine and going
home for the night which means I cannot put modifications
out for use.
OR
If I can't do either one of those, are there any easy
solutions to my problem?

Any suggestions would be greatly appreciated,
Michelle

 

[james molinari]

I have an Access 2000 database with no roles or security
passwords. The database is split and many people have
access to the front end which resides on a shared server.
So, users are not using a copy of the front end, they are
all accessing the same copy.

Without going to the trouble of creating individual user
accounts, is there anyway I can capture the network login
of anyone who has the front end open?
OR
Is there any way I can boot off all users? Some users are
leaving the application open on their machine and going
home for the night which means I cannot put modifications
out for use.
OR
If I can't do either one of those, are there any easy
solutions to my problem?

Any suggestions would be greatly appreciated,
Michelle

 

[Tony Toews]

I have an Access 2000 database with no roles or security
passwords. The database is split and many people have
access to the front end which resides on a shared server.
So, users are not using a copy of the front end, they are
all accessing the same copy.

However you really want to put the FE on each machine or place in a
user specific directory on the server. This will help avoid some
weird error messages when users are changing the same forms record
source, filters and such as well as corruptions.

I specifically created the Auto FE Updater utility so that I could
make changes to the FE MDE as often as I wanted and be quite confident
that the next time someone went to run the app that it would pull in
the latest version. For more info on the errors or the Auto FE
Updater utility see the free Auto FE Updater utility at
http://www.granite.ab.ca/access/autofe.htm at my website to keep the
FE on each PC up to date.

Without going to the trouble of creating individual user
accounts,

Presumably you mean Access user accounts. And that the users already
have individual network accounts.

is there anyway I can capture the network login
of anyone who has the front end open?

While this has a different objective the following will work:
Determining the workstation which caused the Microsoft Access MDB
corruption
http://www.granite.ab.ca/access/corruptmdbworkstation.htm

Is there any way I can boot off all users? Some users are
leaving the application open on their machine and going
home for the night which means I cannot put modifications
out for use.

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