>>I'm amazed that nobody here has EVER in the past decade made a comment about this incorrect behavior. There are several posts about the problem, but never it was said that it's a bug, including your posts.
>>
>>It is important for developers to be aware of the incorrect behavior, because it makes it a requirement to do no direct COPY TO TYPE CSV or APPEND FROM TYPE CSV. Instead, one should write a bug-aware function that does create or read.
>>
>
>I think that before complaining about the CSV implementation in VFP, one must know the standard, and the truth is that the standard explains perfectly how special characters, like double-quotes, must be used in different situations:
>
>https://tools.ietf.org/html/rfc4180
>
>You will find the quotes treatment in page2.
>
>What is amazing to me, is that some people think that CSV is "just" values sepparated by a comma, but didn't research to really know the necessary details involved in the treatment of this type of file.
>
>Update: In wikipedia is well explained too, with some examples including quotes:
>http://en.wikipedia.org/wiki/Comma-separated_values
>
>Update 2: Problem is that VFP expects that double-quotes where escaped, and do not do this automatically, as one expects.
>
I referred to both the rfc4180 document and wikipedia in my first post. It was the VFP-team that hadn't read the rfc4180 document well enough.