Cetin,

I think there's nothing to fix. It's not a bug since XL5 had a limit of 16K. However, what they *should* do is add a new keyword XL8. Whether that will ever happen I don't know.

With regards to the codepage conversion when using FOX2X. There's obviously no problem when you USE the table with FoxPro. However, if you open the table with Excel, a conversion problem occurs. You have to add an AS 850 to the COPY TO command and most characters translate correctly. I noticed a problem with the character "ã" which Excel translated to "╞". I don't remember if there were any other characters that had problems.

>Mike,
>Not fixed and I think will never be (Never say Never < bg >)
>Unless Excel automation is used fox side simple commands have disadvantages. CSV and Fox2x break the rowcount limit but still has spreadsheet rows limit. Fox2x truncates long fieldnames (BTW doesn't lack codepage conversion).
>Both CSV and fox2x fail on transferring memo fields succesfully.
>If you don't have memo fields and rowcount is under current limit (65535 - 1 header line) simpliest is CSV IMHO. In VFP5 you could use Fox2x or delimited file.
>In FoxyClasses DBF2Excel solves the problem by extending rows to multiple sheets + uses ADO when necessary.
>Cetin