A while back I had a bad log file and you folks helped me figure out that it
had accidentally been converted to Unicode format. This caused endless
"corrupt logfile lines" in my Analog report. After that, I became very
careful about what software I used to open and save a log file.
The problem is back except that it now afflicts a batch of NCSA Common
Format logs from our IIS server on an NT. I looked for a simple method of
converting these from Unicode to ASCII without luck.
Now I'm wondering how this could happen in the first place. I know NT
supports Unicode but I wouldn't think there would be a setting somewhere
that would tell it to write logs in Unicode??? The only thing I did that
could have influenced all the log files was to use the Windows/NT "Copy" and
"Paste" commands to copy to logfile directory from the server to my hard
drive. Could this cause ASCII-to-Unicode conversion?
Keith Purtell, Web Designer
VantageMed Corporation
"Your source for software solutions
in medical and dental practices."
------------------------------------------------------------------------
This is the analog-help mailing list. To unsubscribe from this
mailing list, send mail to [EMAIL PROTECTED]
with "unsubscribe analog-help" in the main BODY OF THE MESSAGE.
List archived at http://www.mail-archive.com/[email protected]/
------------------------------------------------------------------------
