This seems so simple and I am missing something big:

In parsing a 500 character row of data sourced from a Unix-based CSV file, that string can sometimes contain an errant mid-row (and NOT at the intended row end) Carriage Return (0D). It's clear the 0D character is there when looking with my Hex Editor. Excel seems it the same. When I move the entire row to a STRING variable and use POS to search for 0D in the string, it's been removed and worse, the next row of data is concatenated. That subverts the error checking.

I'd love to hear what ideas others might have to deal with this.