Logging Username info when query is modified

[Bartcom2000]

Ok guys and gals,

I work in a firm that uses several ms access dbs to reconcile data for multiple accounts. Problem is that many people have acces to the database window. inevitably individuals will go into our production queries and modify them inorder to get answers to their questions. Problem is that they some times forget to change them back or create new queries that leave the origionals untouched. One of the individuals is our president. Needless to say if the query is modified then our data result differs each month which really frustrates us and no one remembers changing the query.

I would like to utilize some code, if possible, that logs the machines system username and date/time every time the save command is activated in a query. I am not really sure how or if this is possible. we all work on a standard window xp network in MS access 2003. It would be real helpful if i could see who made changes to our queries and when. any ideas would be greatly appreciated. also, it is important that the solution not include forms or be too rigorous to imploy. an Auto excec macro w/ corresponding code module would be satifactory. anything more would not be accepted by the group.

[Delerna]

Hmm....I don't know if that is possible.

I have a suggestion though.
1) Put the tables into one database(The Backend)
2) Put everything else into another database (The Front End)
3) Put the backend somewhere that everyone has access to.
4) Create links in the frontend to the tables in the backend.
5) Give everybody their own copy of the front end on their computer.

Now if someone changes a query it will be changed on their own copy.
The only person they will affect is themselves
Problem solved
:)

[Bartcom2000]

yeah, thought of something simular but it is not feasable here. I am just frustated with all the changes. there must be some way to log changes made to elements of a database. Thanks so much for your time........

[timbo82]

I don't think that Access will allow you to create a log in the way that you describe. You could activate file auditing on the server which will keep a log of when the database was accessed and by who but it wouldn't give enough detail to say what was amended.

Could you take a copy of the query and save it for your own purposes? You could call it something obscure that people wouldn't meddle with and then at least you could be reasonably sure of its integrity.

Failing that perhaps a beating with a large stick may be in order?

[Bartcom2000]

lol.... I have tried the stick method, does not work well with employment longevity. But I will keep trying to figure out how to monitor modifications. Keeping a personal copy is one method, it just seems a little cumbersome and archaic..... I may have to do that though. One would think that if you can acces menue commands that you could also acces the comand events like OnClick and such.