>>Hi,
>>
>>>One problem that can be ellusive with SQL Server is if a char field has an apostrophe in it, you need to double the apostrophe before inserting into SQL Server. So Jone's becomes Jone''s.
>>
>>Thanks Jim (and Jordan)
>>In fact the problem seems to be a one character field name in the VFP table - viz. 'i'
>>I changed this to 'ix' and the export suceeded. Oddly enough other one character field names, such as 'k', did *not* cause a problem.......
>>
>>Best,
>>Viv
>
>Hi Viv,
>
>I would call this a bug. But since single letter variables from a to j are not recommended, they may be excluded for field names also in the upsizing wizard.

I agree with you. I also like to avoid cryptic field names. When you visit a table one year down the road you often wonder, “What is this field for”? :)