Pros and cons of using CurrentUser() as security feature?

[RobinK]

I'm using Access 2003.

Instead of using passwords for my database, I used the CurrentUser() feature
on my form to protect records. I's working great! And since I'm a novice,
I'm a little leary that it's working so well.

My tblProjectMgr has a field (updated only by me) that lists the user's
Windows ID. There is an unbound text box (hidden) on the form, where the
control source is set to "=CurrentUser()".

The 'on open' event of the form compares the the Windows ID field to the
CurrentUser value. If they don't match, then an error message appears
telling the user that they cannot edit the record. Otherwise, the form opens
to allow editing.

The company I work for is small, so this method works well.

Any pros or cons with this method?

thanks!

 

[John W. Vinson]

Any pros or cons with this method?

Like an inexpensive door lock, it will keep the honest people out. It would
take someone knowledgable about Access five minutes to crack it. If that's ok,
and meets your needs, go right ahead; it's certainly easy enough to maintain.

John W. Vinson [MVP]