>Hi Cetin
>
>I used the conversion to .csv in the past too, but I struggled here over something, that might be a bug in Excel 2000. I didn't explore it further then, because I switched to the ODBC method.
>
>But I noticed that Excel doesn't always import .csv files properly. The reason for that is that Excel don't use the comma as field delimiter by default for .csv's as you or at least me might expect. It uses the character that is set up as list delimiter in the Windows settings and this is in Swiss German setup the semicolon. So the imports of a real .csv like VFP creates them, don't look very accurate. :-)
>
>As I said I haven't explored this for other language settings of Windows and other OS types than NT4 but I then thought, I'd be safer to just avoid it at all.
>
>Regards
>Markus

Right Markus,
We Europeans suffer of Excel's behaviour on list separator (mine is semicolon too :(). For that reason in one of my projects instead of simply providing a list of ranges in one single range(RangeA,RangeB...) command I sorted to use union ranges command :)
However VFP can save delimited with different qualifiers and Excel has opentext method that you can define delimiters and qualifiers as well.
Cetin