Query Err Msg: "Non Unique Column Reference" with dBASE Tables

Last reviewed: September 12, 1996
Article ID: Q118962
The information in this article applies to:
  • Microsoft Query for Windows, version 1.0

SUMMARY

In Microsoft Query version 1.0, if you add field headings from a dBASE (.DBF) table to the data pane, and if the table has duplicate column names, you will receive one of the following error messages

   Non unique column reference: <field name>

   -or-

   [Microsoft][Single-Tier Driver]Non unique column reference: <field name>

where <field name> is the name of the duplicate column heading in the table.

WORKAROUND

To work around this problem, open the dBASE file in Microsoft Excel and rename or delete one of the duplicate column names from the list. If you delete one of the duplicate columns, do the following to redefine the new list range:

  1. Select the new list range, including the field headings.

  2. From the Insert menu, choose Name.

  3. In the Names In Workbook box, type "Database" (without the quotation marks).

  4. Choose OK.

MORE INFORMATION

In Microsoft Excel, it is possible to create a dBASE file with duplicate column headings. Because Microsoft Excel has limited database capabilities, it does not check the integrity of the database in the file when it is saved in the dBASE file format. When you use Microsoft Query to query data in the file, you may receive the error message described above.


KBCategory: kbinterop kberrmsg
KBSubcategory: xlquery

Additional reference words: 1.00



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: September 12, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.