>Steve,
>
>>I interpret the help to mean than you can import those versions of foxPro tables directly, without ODBC
>It WOULD seem that way, but...
>
>>Did importing as dBaseIII file not work?
>no ;-(
>
>Maybe I'm missing something here...this is what I'm doing - seems simple!
>
>I open my table in VFP 6 and use the COPY TO TestAccessV2 Fox2X; a file TestAccessV2.DBF is created.
>
>In Access 2000:
>- I choose the menu option FILE, GET EXTERNAL DATA, IMPORT
>- find my directory
>- choose "Files of Type" dBASE III
>- click directly on the file TestAccessV2.DBF in the list of files (I don't TYPE the name of the file)
>- I get the error message "The Microsoft Jet database engine could not find the object 'TestAccessV2.DBF '. Maks sure the object exists and that you spell its name and the path name correctly."
>
>Help tells me that possible causes are:
>- file does not exist
>- name was misspelled
>- trying to open a Btrieve table...blah, blah
>
>I get the same thing whether I use "Files of Type" dBASE IV, dBASE 5.
>
>I also tried COPY TO TestAccessPlus FoxPLUS, w/"Files of Type" dBASE III, dBASE IV, dBASE 5.
>
>Thanks for your interest in this...I'm going to check out some earlier versions of Access, but this worries me, in that probably someday my client will be using Access 2000.
>
>J

Sorry Jill. I'm just getting back to the UT after being off for a few months for surgery. I saw your request for
someone to test importing into Access 2000 before I saw this thread. I had the same problem when trying to import
a different table into Access 2000. The solution was to change the file name to 8 characters or less. Don't know why
the Jet database engine can't use long file names, but it seems to have a problem with them. Hope this helps!

Criss