As far as I know, there is no way to trap that information; but you can
prevent the behavior in a couple of ways:
1. Split your database into a front-end (containing all queries, forms,
reports, macros, modules and local-use tables) and a back-end (containing
only shared data). Then (after making a copy of the front-end MDB file),
convert the front-end into an MDE file, using Tools|Database Utilities|Make
MDE file. An MDE file is "just like" an MDB file, except that there is no
capability to make design changes, except to Queries or Tables. Each user
will have their own copy of the front-end installed on their hard drive.
The front-end will contain links to the back-end tables.
2. Implement Access Security - not for the faint-of-heart. Here is a link
to the FAQ for this subject:
http://support.microsoft.com/?id=207793
Using Access Security you can create groups which have specific permissions
to do certain things within the database, among them, making design changes.
hth,
--
Cheryl Fischer, MVP Microsoft Access
Law/Sys Associates, Houston, TX
Jennifer Johnson said:
I have inherited an Access Database on a multi-user network. The problem
is that someone thinks it's "a hoot" to modify a particular form. I need to
know who is doing it so I can take steps neccessary to permanently stop this
type of behavior. Can any one help?