XL98: Problems Adding Text Database in Microsoft Query

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

SYMPTOMS

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

   Error Adding Table
   ------------------

   When you try to add the database (table) to Microsoft Query, the
   following error appears

      Can't access table <database>

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

   Cannot See Database File
   ------------------------

   When you attempt to create a new data source name (File DSN), some or
   all of the database files do not appear in the "Select a default table
   for your data source (optional)" box in the "Create New Data Source"
   dialog box.

CAUSE

Error Adding Table

This problem occurs when either of the following cases is true:

Case 1:

  • You create a File DSN without first creating a User DSN that defines each of the database files.

    -and-

  • In the Add Tables dialog box, you try to add one of the database files that was not defined in the User DSN.

Case 2:
  • You create a User DSN for a text database and the database file contains a file name extension, such as .txt.

    -and-

  • In the Add Tables dialog box, you try to add one of these database files.

Cannot See Database File

This problem occurs if you have not defined that database file by creating a User DSN.

WORKAROUND

To work around this problem, use the following appropriate method.

Method 1: Error Adding Table

To use this method, follow these steps:

  1. Create a User DSN by using the Text ODBC driver and define each table that you want to use.

        a. To define a table, click the Define tab and select your file in
           the list.
    

        b. If the column names do not appear in the Column Information list,
           click Guess, and then click OK.
    

    If you are using several text database files, you must define each by repeating steps a and b.

  2. If your text database file contains a file name extension (such as .txt), configure the DSN following these steps:

        a. When you define the User DSN, click the option "Use DOS File
           Extensions" in the Mac File Types dialog box.
    

        b. After you create the User DSN for the Text ODBC driver, create a
           File DSN for the specific text database file.
    

        c. To add a table to your query, you should use the Query Wizard. If
           you do not use this wizard, the "Cannot Access" error message may
           appear when you attempt to add a text database in the Add Tables
           dialog box.
    

Method 2: Cannot See Database File

If the database file does not appear in the list, first define the table. To define the table when you create the User DSN, follow these steps:

  1. To define a table, in the Microsoft 3.01 Text PPC dialog box, click the Define tab, and select the file in the list.

  2. If the column names do not appear in the Column Information list, click Guess, and then click OK.

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
Keywords : xlquery kbtool
Version : MACINTOSH:98
Platform : MACINTOSH
Issue type : kbbug
Solution Type : kbpending


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.