![]() ![]() Of course, this type of audit log stores the history on the same record as the current values. ![]() So what happens to the history when you delete the record? The history gets deleted along with it. If you’re concerned about this dilemma, why not simply capture the history to a background table through a scripted process before deleting the record? A variety of solutions have been proposed to address this situation. If you know of an easier way to add an audit log to a FileMaker solution, we’d love to hear about it.Įnjoy using this revised version of the FileMaker Pro audit trail technique! The _audit field in this technique is also no longer dependent on a modification timestamp field in each table. * *This article is provided for free and as-is, use, enjoy, learn, and experiment at your own risk – but have fun! eXcelisys does not offer any free support or free assistance with any of the contents of this blog post. If you would like help or assistance, please consider retaining eXcelisys’ FileMaker Pro consulting & development services.Ībout eXcelisys, Inc.: Founded in 2001, eXcelisys ( an FBA Platinum Partner and FileMaker Certified developer organization. eXcelisys specializes in designing, developing, customizing, supporting, consulting, migrating, upgrading, fixing, and integrating of database solutions for Desktop, Mobile, and Web applications. Our core technology competencies are FileMaker Pro, FileMaker Go, and MySQL for database frameworks, along with FileMaker WebDirect, WordPress, MySQL, PHP, CodeIgniter, PostgreSQL, Joomla, Drupal, Magento, CSS, HTML5, and Javascript for web sites and web applications. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |