Tracking Users in an Access 2000 database

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

What is the best way to design an Access 2000 database to track users; by
tracking I not only mean when they are signed on, but what records they enter
into tables, etc.

Any help with this subject would be greatly appreciated.
 
You must implement User Level Security. Once that's done, you can
detect the current user via the CurrentUser() function. You can add
code to the BeforeUpdate event of your forms to capture the name of
the current user, and store it in a field of your table. You will need
to supply some startup code to your application to detect when the
user logs onto your database.

The website in my signature contains links to several references about
how to implement User Level Security. You should practice on a dummy
database before tackling your production database.



Hi,

What is the best way to design an Access 2000 database to track users; by
tracking I not only mean when they are signed on, but what records they enter
into tables, etc.

Any help with this subject would be greatly appreciated.
Click to expand...

**********************
(e-mail address removed)
remove uppercase letters for true email
http://www.geocities.com/jacksonmacd/ for info on MS Access security
 
Access has no built in functionality that tracks data changes by specific
user, or at all, for that matter. but you can build in the functionality.
see http://allenbrowne.com/AppAudit.html for MVP Allen Browne's method of
creating an audit log, which includes complete instructions and the
necessary VBA code. it works very nicely.

hth
 
PMJI :-)

fascal, Douglas means this.

One of the many steps in implementing User Level Security (ULS), is to
add a password to the Admin user. Once you have done that, each user
must log on with a valid username & password. You could actually do
this step on its own. It would only take a few minutes.

There are many /other/ steps that you must /also/ do, to implement ULS
completely. If you do not do those other steps, anyone with some
knowledge about ULS could easily open your database /without/ knowing a
valid username/password.

So it's really a judgement call, as to whether you do or do not want to
do those other steps. Unfortunately, they are fairly complex, requiring
quite a few weeks of work to get a basic understanding. Whereas adding
a password to the Admin user is easy & quick. That's what Douglas was
getting at here.

HTH,
TC
 
Oops, that's NOT what Douglas was getting at here!

He was suggesting to use the user's Network ID to track who they are.
Sorry, I din't see those words initially.

So fascal, what I wrote is a third approach.

jacksonmacd - use user-level security;
douglas - use Network ID;
TC - use a subset of user-level security.

HTH,
TC
 
Hi:

I implemented Allen Browne's code and when I made changes to the
database and checked the tables they have no data in it. Can someone
assist.

Thanks
 
Back
Top