Did you know that you can track quite a bit of detail about database usage in Inmagic DB/TextWorks? Every textbase can include a log file in which can track opening and closing a database, record locking, and record additions and deletions, including the Windows username of the person editing a record.
Time and time again, this log file has proven useful to Andornot and our clients. When errors appear in records, and especially when they have been deleted, perhaps erroneously, checking the log file usually helps clear up the mystery of when and by whom changes or deletions we made. While recovering a backup may be necessary to undo the changes, identifying how it happened goes a long way towards preventing future issues (as does adding passwords and other security to databases).
Full details and options for enabling textbase logs are provided in the help built in to DB/TextWorks. Just press F1 and read the entry for "Textbase log files." Here are some excerpts:
Textbase Log Files
For each textbase, you can enable a log file to record textbase activity, including record and structure changes. A log file is a standard ASCII text file. It is saved in the same location as the textbase and has the same file name as the textbase, with the extension .log. You can enable, view, print, or delete a log file from within DB/TextWorks.
Note: A log file does not record activity performed using Manage Textbase Elements.
To enable a textbase log file
Choose Maintain > Edit Textbase Structure > Log File.
In the Textbase Log File dialog box, select Enable Logging to File.
Select one or two fields with key identifying information that will be written to the log file. We usually recommend selecting the Record ID field if you have one, plus the Title or similar key name field.
To record user activity in the textbase log file
You can add a Details = parameter to the [LogFile] section of the <textbase>.ini file if you want the textbase log file to record who is opening the textbase, editing records, and locking records.
Details = 2
You can set this to one of the following:
0 - No enhanced logging
1 - Logs when a user opens or closes the textbase
2 - Logs when a user modifies records (and opens/closes the textbase)
3 - Logs when a user locks/unlocks record (and opens/closes the textbase or modifies records)
The <textbase>.ini file will be located with all the other database files, including the log file.
See our series of "Spring Cleaning" blog posts about other recommended textbase management tasks.
Contact us for assistance setting this up, or for any other aspect of using DB/TextWorks.