Log file processing is really sophisticated action.
If you select bad method to process LOG file (for instance, the first ;-) ), you probably can be the cause of falling your OS down.
Log file can be processed in three user ways:
Rearrange all log data to a special working DBF table, and load from it.
Direct processing LOG file.
Automatic detection.
Rearrange all log data to a special working DBF table, and load from it
This technique need very much of disc space for their working files.
For these reasons it's acceptable only for little LOG files.
Acceptable file length on WIN-95/128MB/P200 is cca 1MB, and on WIN-NT/128MB/P200 cca 2MB.
But this method is very handly and quick to use.
Direct processing LOG file
This technique is used if LOG file have great length, or if on disc have not enough the space for standard using previous processing method.
Automatic detection
This method is used as default.
By choosing maximal lenght of LOG file you can use processing method.
Under length n MB is used first processing method, and over other processing method.
If source file dosn't exist, then:
During processing LOG file can be happened, so file of source code is not presented on disc at the directory, as write in LOG file. That's a standard situation, if code is traced in APP or EXE. For this case you can select program behaviour:
Go to next file - processing of LOG file will be continued, source code for this file will not be displayed.
Open a dialog - a opening dialog for file selection will be displayed. If no file wil be selected, no any source code for this file will be displayed.