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
Groet,
Peter de Valença
Constructive frustration is the breeding ground of genius.
If there’s no willingness to moderate for the sake of good debate, then I have no willingness to debate at all.
Let's develop superb standards that will end the holy wars.
"There are three types of people: Alphas and Betas", said the beta decisively.
If you find this message rude or offensive or stupid, please take a step away from the keyboard and try to think calmly about an eventual a possible alternative explanation of my message.
