ESHA software does have a basic auditing functionality (which is ‘off’ by default). The auditing is such that, while enabled, the program will automatically record the date/time as well as the login authentication of the user upon Save of a recipe, ingredient, person (Food Processor only), menu plan (Food Processor only), Food Menu (Genesis R & D Only) or advanced label (Genesis R&D only). In addition to saving this information, there is a Comments popup box presented to the user upon save, meant to allow them a way to record what change(s) they’ve made to the record. This Comments box is optional (can be left blank) – and in that event, the audit trail still records the date & login.
To view a particular document's history, with the record open the item select the Audit Trail button (Recipe tab for Recipes, Ingredients tab for Ingredients etc...)
To enable the Audit Trail, there is a setting that needs to take place in the database.
If you are using the ESHA instance of SQL Server to host the database, use Database Utility and connect to the proper SQL Server and the ESHA Database. Note: under Windows Vista, Windows 7, or Windows 2008 Server, you must right-click Database Utility and Run As Administrator. Once connected, you can enable the Audit Trail by clicking Users / Enable Audit Trail.
If you are using your own instance of SQL Server to host the database, you may update the proper row in the database to enable Audit Trails:
UPDATE UPreferences SET PreferenceValue = 1 WHERE OwnerID = 0 AND PreferenceName = 'ShowAuditTrail'
Setting the above to PreferenceValue = 0 will then disable the audit trail.
Note: Enabling (or disabling) the Audit Trail must take place when all users are out of the client application. Settings are not kept if anyone is running the program while changing the setting.
See below for an example of using the Audit Trail Feature