"General" Tab - Basic Settings
The Use advanced settings checkbox allows you to toggle between the Basic and the Advanced interface. The Basic interface has everything you need to use the FullRecord template to its full extent without any clutter, while the Advanced interface gives you the chance to customize the template to the full.
Some tabs like the Global Tab will be available only in advanced mode.
Disable Field Inspect: Check this option if you want to disable this feature. Uncheck it to enable this feature.
Field Inspect Procedure name: Select the procedure from the drop down list which will allow you to inspect the changes made to a particular field. If you leave this field blank, it will default to BrowseAuditField. If you want to disable this feature, you need to tick the "Disable Field Inspect" checkbox above this option.
In a multi-dll system, this Inspect procedure needs to be in the data-dll app to make use of the Template defaults. If you place it in another app, you will have to change several things manually which is possible, although not advised.
Global Hot Key: This is the key you will press when a field on any of your application’s window is selected and you want to see the change history for that field. By default it is set to Ctrl+Shift+A but you can change it to whatever you want, or leave it blank to disable this feature.
Note: when you disable this feature by leaving the Hot Key blank, no code related to the field inspect feature is actually generated.
Disable Record Inspect: Check this option if you want to disable this feature. Uncheck it to enable this feature.
Record Inspect Procedure name: Select the procedure from the drop down list which will allow you to inspect the changes made to a particular record. If you leave this field blank, it will default to BrowseAuditRecord. If you want to disable this feature, you need to tick the "Disable Record Inspect" checkbox above this option.
In a multi-dll system, this Inspect procedure needs to be in the data-dll app to make use of the Template defaults. If you place it in another app, you will have to change several things manually which is possible, although not advised.
Global Hot Key: This is the key you will press in any Form or Browse window to see the change history for the selected record. By default it is set to Ctrl+Shift+R but you can change it to whatever you want, or leave it blank to disable this feature.
Note: when you disable this feature by leaving the Hot Key blank, no code related to the record inspect feature is actually generated.
User identification: The "User" global variable is the variable that will receive the active user code or name for your system. This variable should be populated by your login security system, and may be any data type you want (either for a code or to store a full name). In the FullRecord examples our variable makes use of a numeric code.
Options available for multi-dll systems:
Use local procedures in this app: This option is only visible if your app is a dll and it is not the data dll, it will also be hidden if your app’s target is “exe”. When you tick this checkbox you will be able to activate all the Template tabs, for using the control templates in this particular app.
You can see this option being used in a multi-dll example, check FullRecord’s Global Extension in FRInspect55.app or FRInspect66.app.
Note: You may need to close FullRecord’s Global Extension and reopen it to make all the tabs visible after activating this option.
Include external reference to BrowseAuditField: In a multi-dll system, you'd normally have to include an "external" reference to the BrowseAuditField procedure for each app that has a reference to the data app. If you leave the default procedure name as is, you can tick this checkbox and the external reference will automatically be included for you.
Include external reference to BrowseAuditRecord: In a multi-dll system, you'd normally have to include an "external" reference to the BrowseAuditRecord procedure for each app that has a reference to the data app. If you leave the default procedure name as is, you can tick this checkbox and the external reference will automatically be included for you.
"Change" operation mode:
This part allow you to select how the audit will work for you in this program. There are three modes available, that will allow you to select how the CHANGES to your bases are saved. INSERTS and DELETES are always saved as Full Records.
Always Full Record
This is the same as FullRecord 2.x. In this mode, no matter how many fields are changed at once, the program will save the full record for the file changed. This is convenient if you changed many fields at once, but it can be a space waster if you change only a field or two each time.
If you pick this mode you will work pretty much the same as previous versions of FullRecord.
Always Changed Fields
In this new mode FullRecord will save to the audit file one record per changed field, containing the previous value of the field, and the new (current) value of the field. If you often change only one or two fields, this should save you a lot of space. However, if you change most of the fields of the record, there are two disadvantages, one is you will end with twice as many information saved as in the single-whole record mode, and two, as this mode saves one record per field changed, it can be deadly slow. For example, if you change 20 fields, this will save 20 records to the audit file (as opposite to a single record -or at worst two- for the FullRecord mode).
Mixed
Trying to look for the best of both worlds, we developed this mode where if the number of changed fields are up to so many, the changed fields only are saved, and beyond that number, the whole record is saved. You have to set up the nnumber in the "Max. no. changed fields" entry that is enabled when you pick this mode.
For example, if you enter "6" here, when you change the value of one, two, three or up to 6 fields, the system will save one record per field changed. If you change 7 fields or more, the system will save only one "full" record to the audit base.
So this mode will try to balance speed with file size convenience.
When you use Mixed or Always Changed Fields mode, the Use In-Memory driver in temporary files option becomes enabled.
If you select the Use In-Memory driver in temporary files checkbox, a temporary file needed to store some blob fields will be create in memory, using SoftVelocity's In Memory Data Driver (purchased separately, directly from Softvelocity). If you enable this option and you don't have the driver, you'll get compilation errors.
If you don't select this option the temporary files will be created on disk, in the OS's temporal folder for the current user.