After doing some more research on this, I have found the following: 1. the problem of hex nulls in the log file occurs when using the alternate code for the fix. 2. When the test is started and is in progress, the normal, expected text is in the log file. 3. When the test is completed, then the null characters appear in the log file.
Note the log file is the name of the file on the record task. I can look at other differences in the code. Right now I am puzzled. Suggestions? --glenn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
