>>>>What a nonsense! The COPY TO CSV should have added the second double quote. THERE is the bug.
>>>>
>>>>
>>>>> Everything else is a blind implementation of that idea. Anything trying to implement that without a firm contract between the sender and recipient will be buggy.
>>>>>
>>>>>In this case, the bug is in the "copy to effe type csv" command - it produces this:
>>>>>

txt
>>>>>"is weer "ziek""

>>>>>i.e. it blindly wraps quotation marks around a string containing quotation marks. It doesn't even have a contract with itself. That, yes, that is a bug.
>>>>
>>>>Again, what a nonsense! The APPEND FROM CSV should have converted the double double quotes to a single double quote. THERE is the accompanying bug.
>>>
>>>OMIPU
>>>
>>>Stop complaining. File it to MS. Possibly they will recreate the VFP team to do a bug fix for you.
>>
>>Sorry, I don't know what omipu means. But I'm sure it is not a compliment. About 'complaining': I'm not complaining at all. I'm merely trying to make the readers aware of the fact that there is a lot of denial here and that the bug is a bug is a bug, simple as that. And as I wrote, more developers will gonna get complaints of customers when they upgrade to the latest (?) version of SQL Server. They then search here on the UT and then it's a good thing they read that it's a bug and what workaround is the best way to go.
>
>Bug or not a bug, your message is 20 years too late and your "I know best" arrogance in this case is very annoying. We have all adapted to the reality, meaning how VFP works, and we are fine with it. I suggest that you also accept the realities. If you want a medal for your "discovery", I will send one to you.

The only arrogant person here is you, as your words can be read as "I know better than you, Peter". As I wrote, there is a newer version of SQL Server rolled out in many companies these days that no longer tolerates the input that vfp's COPY TO TYPE CSV produces, so your remark about '20 years too late' is mere nonsense.