|
Import the definitions into your DCT.
| 2. | Export it to TXD (by using the "File","Export text" option inside the Clarion Dictionary Editor). |
| 3. | From the FullRecord example folder (Inside your Clarion folder, look for 3rdParty\Examples\FullRecord), run the TXDAnalyzer program against the TXD just generated. |
| 4. | While you are in your Dictionary import the audit.txd file into your Dictionary. The Audit.TXD file is also located in the FullRecord example folder. |
| 5. | Review the file definitions. The example txd was created with two memo and no blob fields. If you have files that will be audited that contain more than two memo fields or blob fields, you should alter the audit file to include those fields. See the Definitions 1 Tab for a more detailed explanation. Use the results obtained from the TXDAnalyzer program to adjust the memo and record length size settings in the audit files your DCT. |
| 6. | Save your DCT, close it and open your APP. |
Define the global settings in your Data-APP.
| 7. | Press the "Global" button to go to the global area of the data-APP (The data-app is the one where you export all the files and variables definitions). |
| 8. | Press the "Extensions" button to open the global extensions area. |
| 9. | Press the "Insert" button. |
| 10. | Select the "FullRecord" global extension from the list of extensions. |
| 11. | If you want to record the recovered records (recommended), select the "Definitions 3" tab and check the "Record Recover Information" checkbox. |
| 12. | Select the "Files to Audit" tab and select the files you want to audit. If you want to do a quick test of FullRecord’s functionality, just click the "Select All" button. You may also import the file list generated by the TXDAnalyzer program. |
| 15. | Legacy only: Enable the "Enable the use of ABC classes" in the "Classes" Tab, and enable "Enable triggers support" in the "File Control Flags" Tab. |
Import the Inspect Procedure into one of your APP.
| 16. | Choose the FRA6.app example (you will find it in the example folder) for ABC, or FRL6.app for Legacy. |
| 17. | Delete the global extension and do NOT save the app. |
| 18. | Do a selective Export to TXA of the procedures you want to copy (For example, the BrowseAudit procedure). |
You may select one or more of the following procedures:
CleanAudit
BrowseAudit
BrowseAuditBck
BrowseAuditField
BrowseAuditRecord, and
BrowseAuditExtended
| 19. | Close the example app without saving it. |
| 20. | Open your app and import the TXA you just created. |
| 21. | Press the "Global" button to go to the global area of each other APP (including the main app). |
| 22. | Press the "Extensions" button to go to the global extensions area. |
| 24. | Press "Ok" and Enter again into the extension, you will have most of the options visible now. |
| 25. | Select the "Files to Audit" tab and select the files you want to inspect. You should pick the same files you selected in point 12. |
Define the global settings in each other APP.
| 26. | Press the "Global" button to go to the global area of each other APP (including the main app). |
| 27. | Press the "Extensions" button to go to the global extensions area. |
| 28. | Press the "Insert" button. |
| 29. | Select the "FullRecord" global extension from the extension list. |
| 30. | Select the "Files to Audit" tab and select the files you want to inspect. Normally you would pick the same files you selected in point 12 (You can use the TXD Analyzer generated file). |
Steps 26 through 32 are necessary to enable the "Record Inspect" and "Field Inspect" features calls from all the procedures.
Add menu item to your Main app.
| 33. | Add a menu item or items in your main menu to call the procedures CleanAudit, BrowseAudit, BrowseAuditBck and BrowseAuditExtended if you are going to use them. The other procedures will be called automatically by the template. |
| 34. | Compile everything and go. |
MDI WARNING.
If your program has NON-MDI windows or menus, you will need to remove the "MDI Child" attribute from the FullRecord's procedures to avoid a run-time error. You can do that either when creating the TXA or after importing to the new app.
|