Root > Compatibility > 5.x -> 6.x > EurekaLog 6 Documentation > New options > Log File Tab

Log File Tab

Previous pageReturn to chapter overviewNext page   

Caution: this is old EurekaLog 6 documentation. This is not the latest version.




In this section you may customize the log file.


Saving Options:


"Save Log File" Save the log file into the "Output path" folder
"Number of errors to save" Max number of logged exceptions to save (min=1)
"Output Path" The full path of Log File (if is empty then the log is saved into the current program path - if the folder is not writable then the log is saved in the "%UserProfile%/EurekaLog/ProjectName" folder)
"Do not save duplicate errors" Inhibit logging exceptions that have already been logged to the log file (Inhibiting it's send too)
"Append 'Reproduce Text'" Append to the Log File a text, entered by the user of your program, describing How to reproduce the error
"Delete the Log at version change" Delete the Log file when the program version it's changed
"Add 'Computer name' in Log file..."Add the Computer-Name to the Log file name
"Save Modules and Processes Sections" Save the Modules and Processes sections in the Log File (displaying it in the Exception Dialog)
"Save Assembler and CPU Sections" Save the Assembler and CPU sections in the Log File (displaying it in the Exception Dialog)





You may select the type (Application, Exception, etc.) and sub-type (Name, Date, Module, etc.) of the exceptions you wish to store in the log-file.

Send feedback... Build date: 2021-11-08
Last edited: 2018-06-14
The documentation team uses the feedback submitted to improve the EurekaLog documentation. We do not use your e-mail address for any other purpose. We will remove your e-mail address from our system after the issue you are reporting has been resolved. While we are working to resolve this issue, we may send you an e-mail message to request more information about your feedback. After the issues have been addressed, we may send you an email message to let you know that your feedback has been addressed.

Permanent link to this article: