-
Added DataGuard_StartEdit () function to remove requirement to INIT log for existing databases and requirement to maintain ANY data in log and to improve logging performance, especially in large solutions.
-
Modified DataGuard_PostDelete to write a backup version of the record's current data (without field filters) to the AuditLog to ensure a valid and complete version of the record is available for Roll Back.
-
Added DataGuard_LogReflect ( fieldName {; type {; overrideTableName } } ) function to provide quick access to log information (see item #4 below for implementation details).
-
Added DataGuard_Difference ( before ; after ) function to provide a marked up comparison of the before and after parameters submitted, utilizing style and color to indicate Add, Change and Delete operations performed on the after content as compared to the before content. AuditLog table has been modified to contain an unstored calc with this function and the fmDG_Example database has been modified to use this field instead of showing both the before and after fields in the ShowChanges portal.
-
Modified error reporting -- strings have been replaced by error codes to enable enhanced documentation and support, as well as better international localization. See /Documentation/fmDG_ErrorCodes.txt for coomplete listing.
-
Modified internal collection of field list information to introduce Field List Caching. In fmDG 1, each DataGuard_PostEdit function call independently compiled the listing of fields to track by performing a query on the log to collect the TableSchema entry, and then cross reference this with the Exclusion Prefixes and/or Custom Field List submitted in the function call. In fmDG 2, this process occurs once every 5 to 7 minutes. This dramatically improves the speed to perform logging, especially noticable for batch operations. It does mean, however, that if a new field is added to a database from a development machine on the network and UpdateSchema is performed to introduce this new field to be logged, that active users on the network may not begin logging changes to that field for up to 7 minutes.
-
Modifier name - The plugin now sets the modifier name based on the Active Account Name in the source file rather than that in the AuditLog file, hence removing the need to mirror account names from source files in the AuditLog or use the Optional Field Name/Value parameters to overwrite the Auto-Entry options in this field in the AuditLog.
-
Added DataGuard_GetLastError function to return the last error code captured by the plugin. This function retains the last error logged, so it is not a place to check whether the last function call succeeded.
