[AccessD] Delimiter Value

[Stuart McLachlan]

Similar problem  with Unix generated text files which just use a LF (Chr$(10) as the delimiter 
rather than the Windows CR LF pair.

VBA doesn't recognise this as a line break and if you use Line Input..., it tries to {ead the 
whole file in one go.  You need to do a universal Replace of LF with CRLF before trying to 
parse

I ended up writing  a very small pre-processing utility in PowerBASIC to do this when I had a 
few  Access applications that were reading in large Unix generated text data files (many 
hundreds of MB  per file).

And of course, to complicate matters further, early MACs (up to OS 9?) used a single CR as 
the delimiter.  :{


-- 
Stuart

On 5 Mar 2015 at 18:06, Bill Benson wrote:

 
> I found one time that when loading data from Excel into a text box on
> a userform, the cell which had contained a line break character -
> can't remember if it was CHR(10) or CHR(13) gave me infinite pains
> when trying to parse the text in the text box. I forget what Access
> did to it - either converted it to a combination or switched them.
> Whatever it was, it was a major PIA and it made testing values, or
> length of entries a big headache. I wish I could remember what it was
> and I wish I could.
>