Posted by Tom Fulton on June 01, 2004 at 07:13:13:
I had an end-user report an error running a program that had been run
daily for many years. I tracked down the error to an inconsistency
in '@20@' vs '@00@' on a file read. Attached is a text file version
of my work program that demonstrates the inconsistency. Here's what
I've come up with:
If a file read is into a format with a string array, then any array
element that is after the last non-blank character in the record comes
in as '@00@' instead of '@20@'.
The end-users program was reading in a file being transferred over
from a Mac. The program read in from the text file into an array and
parsed out each piece of data, looking for commas and double quotes.
After the last field was read and the last quote was determined and
the next character was blank, the parsing routine stopped and got the
next record. The program was falling down because the next character
was null, not blank. It kept going looking for a blank and got an
array subscript out of range error. The Work program demonstrates this. Thanks in advance, Tom.