Audit Trail Code?

[hi there]

hi everyone,

i distributed an application a little while back and got a call saying it wasn't working. apparently, someone got into the code and tried to tweek it to do something different then it was originally designed to do. it wasn't that big of deal, but i was wondering if there are any precautions i could take to monitor or at least document if any code behind forms/reports has been changed. i'd say in 99% of the time using jet security will work, but at least a couple people will want to have full admin rights. any ideas?

thanks

 

[John.Woody]

I think the most secure way would be to convert your mdb file to a mde file and distribute that file as no one can get to any of the code (not even you). Make sure that you keep a copy of the mdb file for your development and update purposes.

Alternatively if your using Access 2000 or xp you can password protect the vba window so no one can view any code without putting in the correct password.

The top method is Favourite as no one can mess with any fields on forms, changing calculated fields etc.

HTH
John

 

[hi there]

hi john,

thanks for the reply. i've thought about going the MDE route, but i haven't really messed around with it. i think you right about making the FE a MDE. it seems like the simplest and best solution.

thanks