Article ID: 287674 - Last Review: November 6, 2003 - Revision: 4.1

ACC2002: "ODBC Call Failed" Error Message Exporting to FoxPro

View products that this article applies to.
This article was previously published under Q287674
Novice: Requires knowledge of the user interface on single-user computers.

This article applies to a Microsoft Access database (.mdb) and to a Microsoft Access project (.adp).

For a Microsoft Access 2000 version of this article, see 237819  (http://support.microsoft.com/kb/237819/EN-US/ ) .

On This Page

Expand all | Collapse all

SYMPTOMS

When you try to export a table by using the Microsoft Visual FoxPro ODBC driver, you may receive the following error message:
ODBC Call failed
[Microsoft][ODBC Visual FoxPro Driver (#712)
NOTE: You may also receive the following error message
ODBC Call failed
[Microsoft][ODBC Visual FoxPro Driver (#200)
One method for resolving error #200 is to download and install the latest Microsoft Data Access Components (MDAC) from the following Microsoft Web site:
http://msdn.microsoft.com/en-us/data/aa937729.aspx (http://msdn.microsoft.com/en-us/data/aa937729.aspx)
Back to the top

CAUSE

You may receive the #712 error message when any of the following conditions is true:
  • The table name has more than eight characters.
  • At least one field name is more than eight characters long.
  • At least one field name has a space or spaces.
Back to the top

RESOLUTION

You can work around the limitations of the Visual FoxPro ODBC driver by limiting table names and field names to eight characters and by ensuring that field names do not have spaces. Because this correction may be inconvenient because of dependencies within your database, it may be more appropriate to make the changes to a copy of the table, and then to export the result.

Although this workaround has been tested successfully on Microsoft Windows 2000 and Microsoft Windows NT Server and Workstation (SP5), on Microsoft Windows 95, Microsoft Windows 98, or Microsoft Windows Millennium Edition, you may receive the following error message:
The Microsoft Jet database engine could not find the object ''. Make sure that the object exists and that you spell its name and path name correctly.
If you receive this error message, use Notepad to create a zero byte file. Save it as <prefix>.dbf, where prefix is the name of the table to be exported. The path name will be the location pointed to by the DSN.
Back to the top

MORE INFORMATION

Steps to Reproduce the Behavior

  1. Create a system DSN using the Microsoft Visual FoxPro driver. If your version of this driver is earlier than version 6.00.8440.00, you can download MDAC 2.1.2.4202.3 (GA) from the following Microsoft Web site:
    http://msdn.microsoft.com/en-us/data/aa937729.aspx (http://msdn.microsoft.com/en-us/data/aa937729.aspx)
  2. Create a new blank database.
  3. Create the following table:
       Table: tblTestTable
   ----------------------------
   Field Name: pkeyID
   Data Type: AutoNumber
   Indexed: Yes (No Duplicates)

   Field Name: strLongName
   Data Type: Text
   Field Size: 50
   Indexed: No

   Table Properties: tblTestTable
   -------------------------------
   PrimaryKey: pkeyID
  4. Open the table in Datasheet view, and then enter some sample data.
  5. On the File menu, click Export.
  6. In the Save as type box in the Export Table 'tblTestTable' To dialog box, click ODBC Databases().
  7. In the Export dialog box, leave the table name as tblTestTable, and then click OK.
  8. In the Select Data Source dialog box, click the Machine Data Source tab, select the DSN that you created in step 1, and then click OK.

    Note that you receive the error message that is mentioned in the "Symptoms" section of this article.
Back to the top

REFERENCES

For more information about setting up ODBC data sources, click Microsoft Access Help on the Help menu, type set up odbc in the Office Assistant or the Answer Wizard, and then click Search to view the topics returned.
Back to the top
APPLIES TO
  • Microsoft Access 2002 Standard Edition
Back to the top
Keywords: 
kberrmsg kbprb KB287674
Back to the top
 

Get Help Now

Contact a support professional by E-mail, Online, or Phone

Article Translations

 

Related Support Centers