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

Article translations Article translations
Article ID: 237819 - View products that this article applies to.
This article was previously published under Q237819
This article has been archived. It is offered "as is" and will no longer be updated.
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 2002 version of this article, see 287674.
Expand all | Collapse all

On This Page

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

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.

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 Windows NT Server and Workstation (SP5), on Windows 95 or 98, 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.

More information

Steps to Reproduce 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
  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 enter 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 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 described in the "Symptoms" section of this article.

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.

Properties

Article ID: 237819 - Last Review: October 26, 2013 - Revision: 4.0
Applies to
  • Microsoft Access 2000 Standard Edition
Keywords: 
kbnosurvey kbarchive kbprb KB237819

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com