Microsoft KB Archive/95327

= ACC: Error When Importing dBASE, FoxPro, or Paradox Table =

Article ID: 95327

Article Last Modified on 1/18/2007

-

APPLIES TO


 * Microsoft Access 1.0 Standard Edition
 * Microsoft Access 1.1 Standard Edition
 * Microsoft Access 2.0 Standard Edition
 * Microsoft Access 95 Standard Edition
 * Microsoft Access 97 Standard Edition

-



This article was previously published under Q95327



Novice: Requires knowledge of the user interface on single-user computers.



SYMPTOMS
In Microsoft Access 97, when you import a Paradox file that does not contain a file extension as part of its name or does not follow the MS-DOS 8.3 file name format (that is, an 8-character name followed by a 3-character extension), you may receive the following error message:

The Microsoft Jet database engine could not find the object ' '. Make sure the object exists and that you spell its name and the path name correctly.

Note This error may also occur with a dBASE file in Microsoft Access 97, if the file name does not follow the MS-DOS 8.3 file name format.

In Microsoft Access 2.0 and 7.0, when you import a Paradox file that does not contain a file extension as part of its name, you may receive the following error message:

Couldn't find object ' '

In Microsoft Access 1.x, when you import a dBASE, FoxPro, or Paradox file that does not contain a file extension as part of its name, you may receive the following error message:

Couldn't find object ' '



RESOLUTION
Rename the file so the file has the correct extension, such as .dbf for a dBase file.

Note Although incorrect extensions may have been permitted in the past, as of February 2003, current versions of Jet require that the correct file extension is used for security reasons.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

240770 OFF: Frequently Asked Questions About the ODBC Driver Security



STATUS
Microsoft has confirmed this to be a problem in Microsoft Access 1.x, 2.0, 7.0, and 97.



Steps to Reproduce Problem
The following steps use a Paradox file as an example. You can also use a dBASE or FoxPro file to reproduce the error message in Microsoft Access 1.x.

 Rename a Paradox file so that it has no extension. For example, rename Customer.db to Customer. Open a Microsoft Access database. Import the file:

In Microsoft Access 7.0 and 97:

 On the File menu, point to Get External Data, and then click Import. In the Import dialog box, click Paradox (*.db) in the Files of Type box.</li> Type *.* in the File Name box.</li> click the Paradox file that you created in step 1.</li> Click Import.</li></ol>

In Microsoft Access 1.x and 2.0: <ol style="list-style-type: lower-alpha;"> On the File menu, click Import.</li> In the Import dialog box, click the appropriate version of Paradox, and then click OK.</li> In the List Files Of Type box, click All Files (*.*).</li> Click the file that you created in step 1.</li> Click Import.</li></ol> </li></ol>

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

Additional query words: couldn t

Keywords: kb3rdparty kbbug kberrmsg KB95327

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.