[AccessD] Delimiter Value

[Bill Benson]

Totally unrelated ... but I can't stand a thread which ends with the words
"I can't" on this esteemed forum, so I am going to hack the thread....

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.

On Tue, Mar 3, 2015 at 5:17 PM, John W. Colby <jwcolby at gmail.com> wrote:

> No, I can't.
>
> John W. Colby
>
> On 3/3/2015 3:31 PM, Stuart McLachlan wrote:
>
>> Can you refer me to that "standard"?
>>
>> The closest I've ever come to finding one is RFC 4180 which not a
>> standard itself and which
>> includes the wording
>>
>> "While there are various specifications and implementations for the
>>     CSV format (for ex. [4], [5], [6] and [7]), there is no formal
>>     specification in existence, which allows for a wide variety of
>>     interpretations of CSV files."
>>
>> It then continues until you reach this classic absolute classic:
>>
>> "5.  Each field may or may not be enclosed in double quotes (however
>>         some programs, such as Microsoft Excel, do not use double quotes
>>         at all).  If fields are not enclosed with double quotes, then
>>         double quotes may not appear inside the fields. "
>>
>>
>>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>