>>>>>Hey, Igor. These are exact steps, we tried at work. We always got 8char name (I tried couple of times by myself). I'll try at work one more time and I'm going to try it at home right now with Access 2000.
>>>>>
>>>>>Thanks again for the help.
>>>>>
>>>>>UPDATE Ok, I've tried with Access 2000, but I was unable to import data from VFP table. I tried different variations of ODBC, and always got some error...
>>>>>
>>>>
>>>>So are you trying to import or export? The importing from VFP part I was doing just yesterday, (Access 2000) nothing fancy just went with the wizard:
>>>>- Open File menu, select Get External data
>>>>- Select import
>>>>- Select ODBC() from files of type, select DSN.
>>>>- Browse to your DBC or free table dir and the rest is easy.
>>>>
>>>>Make sure you have the latest version of the VFP ODBC driver. HTH
>>>
>>>I was trying both. Where can I get the latest VFP ODBC driver?
>>>
>>>My original problem was with Access 97. I could not export table with a long name (10chars) correctly.
>>
>>It's at http://msdn.microsoft.com/vfoxpro/downloads/odbc.asp. The long table name thing could be a VFP ODBC driver thing.
>
>When the users export file from Access to VFP, the chanracters fields become 254 char long. This is Access 97. Do you know, is it still a problem with the latest Access driver? Is it a problem in Access 2000?

Nadya,

Sorry for the long delay, It's been hectic to say the least. To answer your question, exports from A2K to VFP tables using the latest VFP driver work just fine, no fields coming out with wrong lengths. Even memo fields are converted OK.