In the main app, or in your main-data dll app for a multi-dll system, you have to specify which files you are going to audit.
"Files to Audit" Tab - Basic Settings
The fastest is just to press the "Select all" button to select all the files. The Audit file (with Bck, New and Recover secondary files) and the Messages file defined before are automatically excluded.
If you don't use the TXD Analyzer companion program, in a multi-dll system you have to select the files to inspect in this tab in the same way as you did in the main-data dll, i.e. you have to select the files twice; in the main-data dll and in the dll or exe where the inspect procedure will be. If the inspect procedure is in the same main-data dll (not advisable), then you just need to select the files in that place.
A quick and better alternative way to do this is to use the TXD Analyzer program and Export the Files List. Then you can select here the "Load file list" option, and pick up the file generated by the TXD Analyzer program.
After you select a FIL file here, your files list will be imported into the global extension of the template. Then you can "Select all" the files you want to audit or inspect.
Beware!: This procedure is automatic and will save you a lot of time, but be careful, the "manual" way of selecting files will pick files from a list made from your current DCT, while this automatic import of the list is made blindly; i.e. if you pick the wrong FullRecord.FIL file, you will end with a list of files that don't belong to the current app. The remedy is simple, though; just pick the correct FIL file and the list will be corrected automatically.
When you use the "Load file list" method, the file list is imported into your app each time the app is opened or the global extension is accessed. Your actual file selection inside this list is preserved, but the FullRecord.FIL file referenced here (Generated by the Export Files List button in the TXD Analyzer program) have to externally exists in the indicated path, and it will be needed for compiling the program.
Note also that if you make changes to the external file list, like adding files, those files will not be automatically selected in the global extension, so you have to select them entering the global extension in the app needed.
"Files to Audit" Tab - Advanced Settings
Below that, you can see the following prompts:
These allow you to record the "insert" and "last change" audit data to the original file record (NOT to the audit file). This way you can quickly check in a regular browse for any file when and who inserted the record, and when and who last touched it.
You may select if want to record the date, the time and/or the user code.
You should add in your files 2 fields for each checkbox, for each option one for "inserts" and the other for "changes" (if you mark all the options that would be 6 fields). You can name them whatever you want and put them in your files in any position and order you like.
When you press the "Insert variables" button you'll see:
Here you specify the name of the fields for recording the date, time and user (without the prefix), when the user inserts a new record to any of the audited files. To the right, you specify the value that fields should take (The user variable was already specified above).
As for this example, if you have a PEOPLE file with PEO as prefix, the template will look at three variables named PEO:DateAdded, PEO:HourAdded and PEO:UserAdded (case insensitive, in any order and position within the PEOPLE file definition) and if it found any of them, it'll fill them when appropriate. If the template is instructed to fill these variables, but any of them are not found in the file definition, the unfound variable is just ignored.
When you press the "Change variables" button you'll see:
Here you specify the name of the fields for recording the date, time and user (without the prefix), when the user changes an existing record on any of the audited files. To the right, you can see the values that the fields are going to take. These are shared with the insert variables.