Copy to

[barrymavin]

I have now added SET CSVHEADING ON | OFF (default ON) which will allow you to customize whether or not field headings are included in the csv text file.

This will be available in the next build so give that a try and let me know if that works for you.

[g6649a01@kabsi.at]

I did

create cursor test (f1 int,f2 int)
insert into test values (1,1)
insert into test values (3,3)
lcfile = "c:\temp\test3.csv" && or other similar path. I used an UNC-path of our server

Afterwards:

OK => list
=> provides same behaviour of yours
?? => copy to (lcfile) type csv delimited with '|'
=> generates
OK => I opened this file with Excel via Import external data and choosed Windows (ANSI) instead of selected (??) MS-DOS (PC-8)
=> generates

So the strange "optical" behaviour in windows editor is no problem for me.
I will take a look, why the following BULK INSERT doesn't work as it does in VFP. It doesn't generate a SQLEXEC-error, handle,.. all ok, but the table in sql server is empty. In sql profiler, the statement is also ok, but it doesn't load anything

[g6649a01@kabsi.at]

I found my problem, and can solve it with SET CSVHEADING OFF

I thought, I could ignore "new" headers of COPY TO in sql BULK INSERT by option FIRSTROW=2, but
The FIRSTROW attribute is not intended to skip column headers. Skipping headers is not supported by the BULK INSERT statement. When skipping rows, the SQL Server Database Engine looks only at the field terminators, and does not validate the data in the fields of skipped rows.
=> see http://technet.microsoft.com/en-us/l.../ms188365.aspx

I deleted the first line of produced csv file - as it will be exported with your new SET CSVHEADING OFF - and it works as expected

Thanks, Claus

[barrymavin]

I believe it was because the text file just had a LF rather than a CRLF which I have now fixed. BULK INSERT probably balked at that.

[barrymavin]

Ok thats good. We will make it available in the beta directory next week with various other tickets that we have fixed. I've also increased the text buffer sizes so it should be significantly faster on large amounts of data too as it reduces disk seeks,

[g6649a01@kabsi.at]

Great!

Cool solutions for upcoming problems/differences to vfp, quick response,...