XL98: Problems Adding dBASE Database in Microsoft Query

Last reviewed: February 2, 1998
Article ID: Q179108
The information in this article applies to:
  • Microsoft Excel 98 Macintosh Edition

SYMPTOMS

When you try to query a database in Microsoft Query using the dBASE ODBC driver, one of the following problems occur:

Errors Adding a Table

One of the following error messages appear

   The table name <database> was larger than
   SQL_MAX_TABLE_NAME_LEN from SQLGetInfo(8).

where <database> is the name of the file you are attempting to open in Microsoft Query.

-or-

   Field not found: <fieldname>

where <fieldname> is a field in your database.

When you click OK, you are unable to add tables to your query.

Unable To See Database File

In Microsoft Query, when you attempt to add a table your dBASE database file is not listed.

CAUSE

Errors Adding a Table

The SQL_MAX_TABLE_NAME_LEN error message occurs when you do the following:

  • You create an ODBC User data source and you do not enable Long File Names in the ODBC Setup PPC.

    -and-

  • The database file you select contains a space in the name or the name is greater than eight characters.

    -and-

  • You use the Query Wizard in Microsoft Query.

The Field Not Found error occurs when you do the following:
  • The database file you select contains a space in the name.

    -and-

  • You use the Query Wizard in Microsoft Query.

Unable To See Database File

Your database file will not appear in the Add Tables dialog box when you try to add a dBASE database that was created or saved in Excel.

NOTE: this problem does not occur when you use the Query Wizard. A file saved with a .DBF file extension will be visible in the Query Wizard.

WORKAROUND

Use the workaround appropriate to the specific problem you experience:

SQL_MAX_TABLE_NAME_LEN Error Adding a Table

If you receive this error adding a table to Microsoft Query, do not use the Query Wizard when opening a database in Microsoft Query. This error does not appear if you do not use the Query Wizard.

 -or-

Create a User DSN and set the option to enable long file name support. The Use Long Names option can be set in the Advanced tab when you click Configure in the ODBC Data Source Administrator for your User DSN.

Field Not Found: <fieldname> Error Adding a Table

If you receive this error in the Query Wizard while adding columns, remove the space character from the name of your database file. As an alternative to a space use an underscore character (_).

 -or-

Do not use the Query Wizard when opening a database in Microsoft Query. This error does not appear if you do not use the Query Wizard.

 -or-

Create a User DSN and set the option to enable long file names. The Use Long Names option can be set in the Advanced tab when you click Configure in the ODBC Data Source Administrator for your User DSN.

Unable to See Database File

If your database does not appear in the Add Tables dialog box, do the following to correct this problem:

If you have not created a User DSN, do so. In the ODBC Data Source Administrator, click your User DSN and click Configure. On the Mac File Types tab, make the following changes:

  1. Set the File Creator Type to XCEL.

  2. Set the Database File Type to BINA and click OK.

NOTE: the File Creator Type and Database File Type settings cannot be set for a File DSN.

STATUS

Microsoft has confirmed this to be a problem in the products listed above. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.


Additional query words: XL98 msquery
Keywords : xlquery
Version : MACINTOSH:98
Platform : MACINTOSH
Issue type : kbbug
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 2, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.