ACC: Error When Importing dBASE, FoxPro, or Paradox Table (95327)
The information in this article applies to:
- Microsoft Access 1.0
- Microsoft Access 1.1
- Microsoft Access 2.0
- Microsoft Access for Windows 95 7.0
- Microsoft Access 97
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 '<filename>'. 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
'<filename>' 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 '<filename>' 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.
Modification Type: | Major | Last Reviewed: | 5/28/2003 |
---|
Keywords: | kb3rdparty kbbug kberrmsg KB95327 |
---|
|