Yes. Each solution file requires a Table Occurrence to the AuditLog table, which can reside in any one of the solution files, or ideally, in its own file, and as a Best Practice, on its own FileMaker Server. Are there any limitations or database requirements which must be met? There are a small number of limitations as well as requirements that must be met. See the documentation which comes with the demo download for details.
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?
Comments
0 comments
Article is closed for comments.