Article ID: 209685 - View products that this article applies to.
This article was previously published under Q209685
For a Microsoft Access 97 version of this article, see 95327Novice: Requires knowledge of the user interface on single-user computers.
This article applies only to a Microsoft Access database (.mdb).
In Microsoft Access, when you import a dBase, FoxPro, or Paradox file that does not follow the MS-DOS 8.3 file name format (that is, its name before the period exceeds eight characters, or it lacks a three-character extension following the period), 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.
To avoid this problem, rename the file so that it matches the MS-DOS 8.3 file name format. That is, the file name must be no more than eight characters in length, and it must have a correct extension following the period, such as .dbf for a dBASE file.
Note: Although earlier versions of Jet did not require that you use the correct file name extension, changes to Jet security now require that you use the correct extension. For additional information about changes to Jet security, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/240770/ )OFF: Frequently Asked Questions About the ODBC Driver Security Vulnerability Update
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability or fitness for a particular purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft support engineers can help explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
Steps to Reproduce the ProblemThe following steps use a Paradox file as an example. You can also use a dBASE or FoxPro file to reproduce the error.
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.
Article ID: 209685 - Last Review: June 23, 2005 - Revision: 6.0
Contact us for more help