If you set up user level security (not easy, mind you), you could set it so
that only the db owner can update data in the tables. The rest of the users
will be prevented from making unauthorized changes unless they know how to
circumvent user level security (even advanced level people have trouble with
security).
The mysterious changes will suddenly cease, but you'll have one or more
complainers who "can't do their job!" any more. Have these complainers show
you what they're trying to do, and you'll find the guilty ones. Chances are,
they don't know the results of their actions, so they didn't know they were
making the changes to the wrong records.
Also be prepared to find out the db design makes unintentional changes to
data. For instance, naming a field "Date" is one of the most common mistakes
by new db developers. When a user runs a form, the form can change the date
in a record to today's date. Not the user's fault, but a faulty design could
be this mysterious "fairy" you're trying to nail.
Chris
Microsoft MVP
sharsy wrote:
>Hello,
I have setup an Access Database which about 7 people can enter data
into. We have had a few problems where a 'fairy' has mysteriously been
changing data in the table that they're not supposed to. I was
wondering if it was possible to find out which user is responsible for
making these changes. The database is not password protected or
anything.
Kind regards,
Shari
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200806/1