It's working fine now. Thanks a lot to you and everyone, who helped.

>Nadya,
>
>- control panel\ODBC Data Sources
>- System DSN\Add\Microsoft Visual FoxPro driver\Finish
>- Database type: (o) Free Table directory
>- Path: G:\Redp\Work\PP\Converted\
>
>HTH
>>>Nadya,
>>>
>>>I think you have to use the VFP ODBC driver instead of the native FoxPro (2.x) driver.
>>>
>>
>>How can I set it up? Could you please provide step by step instructions (sorry for being dumb)? I tried it now and it gave me another error. I guess, it doesn't properly set up, so I have to do it.
>>
>>Thanks again.
>>
>>>HTH
>>>>>Nadya,
>>>>>
>>>>>Instead you need to go to Insert, Table, Link/Import
>>>>
>>>>I got the same errors.
>>>>
>>>>>>Hi Igor,
>>>>>>
>>>>>>I open Access 97 blank database. Then I choose Get External Data/Import. File type - Microsoft FoxPro ('DBF'). I select my file G:\Redp\Work\PP\Converted\PR08AGAW01.dbf and got this error:
>>>>>>

>>>>>>The Microsoft Jet database engine could not find the object <name>. Make sure the object exists and that you spell its name and the path name correctly. (Error 3011)

>>>>>>
>>>>>>So, what's the problem?
>>>>>>
>>>>>>
>>>>>>>Hi,
>>>>>>>
>>>>>>>Access 97 and Access 2000 allow to use long object names. For example: "Controls in process/case not interviewed" is a valid name of the query.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Hi everybody,
>>>>>>>>
>>>>>>>>We use long file names for our tables. When we try to load those files in Access 97 using FoxPro as driver, it says "Can not find the file". We think, the problem is in long names. Do you know, is this problem solved in Access 2000?
>>>>>>>>
>>>>>>>>Can we fix it in Access 97 by some settings?
>>>>>>>>
>>>>>>>>Thanks a lot in advance.