Yes. By setting a Transaction ID flag that gets included in your Audit Log, you can use the Roll Back feature to find these entries and roll each of them back, including Add, Change and Delete operations across multiple files, table and records. Note that unlike selecting Roll Back while working with ODBC/JDBC, your changes will be committed to your datasource as you go, but the Audit Log allows you to reverse the changes that were made after the fact. This will not prevent other users or processes from see the initial changes made in the period before you select to Roll Back.
Articles in this section
- FileMaker Compatibility for fmDataGuard 3
- Can fmDataGuard be used to support other types of logging requirements besides data Add, Change and Delete activity?
- Can fmDataGuard be used to provide transaction-level roll back (all or nothing)?
- Does fmDataGuard support Instant Web Publishing and other FileMaker External APIs?
- Does fmDataGuard support multi-file solutions?
- Can I get help implementing fmDataGuard in my solution?
- Is there a demo version of fmDataGuard I can try?
- What is an Audit Log? Why do I need one?
- Does it work on both Macintosh and Windows in a multi-platform office?
- Can fmDataGuard be integrated with an already existing FileMaker Pro solution?