How do I use FailSafe's log file feature?
LOG FILE SECTION
The log file section lets you control writing to disk. The format within the client INI file is:
CAPTURE TO DISK =
WRITE TO DISK =
LOG FILE =
capture to disk entry:
The default for the CAPTURE TO DISK entry is FALSE ( that is, CAPTURE TO DISK = 0). When FALSE, trace messages are not written to disk. When TRUE (that is, CAPTURE TO DISK = 1), trace messages are appended to the disk log file identified under the LOG FILE entry.
write to disk entry:
The default for the WRITE TO DISK entry is FALSE (that is, WRITE TO DISK = 0). When FALSE, error information is not written to disk. When TRUE (that is, WRITE TO DISK = 1) then error information is appended to the disk log file identified under the LOG FILE entry.
log file entry:
The LOG FILE entry is used to contain the complete path and file name (for example, LOG FILE = C:\VB5\ERRORLOG.LOG) where error information is to be written if the WRITE TO DISK entry is TRUE.
If the LOG FILE entry has a filename without a path (for example LOG FILE = ERROR.LOG) then the application path is appended to the log file. For example, if the application is installed under D:\SOMEAPP then the log file will be written to D:\SOMEAPP\ERROR.LOG
IF you know the path ahead of time then using a path is recommended
LOG FILE = C:\YOURPATH\ERROR.LOG
This will write all errors to C:\YOURAPP\ERROR.LOG. IF you do not know the path ahead of time (like when installing an app on a user machine) then leaving the file name only without a path is recommended. For example: LOG FILE = ERROR.LOG