Hoi Peter,

Hoe gaat ie?

For this (and other) reasons, we just build our own CSV generator, but it was after the release of V9 and did not found it to be a big enough problem to put it on the ER list.

Walter,




>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.
>
>>And your point is?
>>
>>>IMO, VFP, including 9, has a bug with regard to the export and import of CSV-files.
>>>
>>>Here is the code that proves this:
>>>

create cursor c_effe ( txt c(20) )
>>>insert into c_effe value ( 'is weer "ziek"' )
>>>copy to effe type csv
>>>append from effe type csv
>>>browse

>>>
>>>How come nobody ever told this to the vfp-team???
>>>
>>>And yes, I know how to prevent this. But isn't that actually a silly situation? It should've been VFP that does the correct handling of double quotes.
>>>
>>>See also: http://en.wikipedia.org/wiki/Comma-separated_values and http://tools.ietf.org/html/rfc4180