I work in an environment regulated by the FDA. A reg added in 1997 (Part 11) requires that electronic records be audit trailed by an independent system and log who changed what from what to what, when.

Using code borrowed from James Ray I've managed to meet the requirement pretty well. Jim's code works, is dependable, and is relatively easy to implement by adding in forms, subforms, agents, views, and a script library.

Jim's code can't detect changes to Rich text or user created smart icon code; to invoke the audit trail, you have to build it into your code.

Trigger Happy fixes all of that and more. This thing runs in the background and detects any change no matter how it's done. It's also less complex to implement - one agent, one script library, one config doc per db (unless you just want to monitor every db then it's one config doc period). Sweet!



I plan to modify the design to allow me to specify where the logs go and how they are generated - one edit, one 'from/to' document with some human friendly document identification so I can easily tell which doc was changed.



What I can't figure out is how to trap this human friendly information related to deletions - I can get the UNID but the stub doesn't have any field data that helps me know that 'the doc related to topic X' was deleted. If I could figure that out…stick a fork in it, you have a system monitoring tool. This isn't actually a huge issue for me because most of my dbs don't allow deletion, but it would be nice to have it anyway.



Wow…just wow - this is just amazing; thank you.



Doug



FWIW - forget the FDA, once we started implementing audit trails, I found them to be a huge value in figuring out why things went wrong in workflows. I can see who touched what, in what order, and have been able to identify gaps in my workflow designs that would not have been possible without an audit trail. If you're not using them, you should be. Like I said, this app really is a game changer.