No,
Howevr, There are two ways to solve the problem of auditing record changes.
1. create a datetime field and update it each time it the record is touched. This tells you when, but not what was edited.
Or
2. (my method) - See Attachment
I have one primary table that I needed to track 200+ data elements
I created a tracking table (tablename_Activiy.db)
Then I created a global objectpal function the was called from the CHANGEVALUE event of the forms that edit that table.
Each time anything on the form is changed, it logs when, who, and the before and after values. I also have a session variable which tracks everything that was changed during a particular login.
It is more work to do this, but if detail is important, then this is the way to go.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.