XL5: Syntax Errors Using Array Fields in MSQuery

 Last reviewed: September 2, 1997
Article ID: Q150375
The information in this article applies to:
  • Microsoft Excel version 5.0 5.0c

WARNING: The information in this article has not been confirmed or tested by Microsoft. Some or all of the information in this article has been taken from unconfirmed customer reports. ANY USE BY YOU OF THE INFORMATION PROVIDED IN THIS ARTICLE IS AT YOUR OWN RISK. Microsoft provides this information "as is" without warranty of any kind, either express or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

SYMPTOMS

When running a query against a Progress database with an OpenLink driver (version 1.1010825) in Microsoft Query version 1.0, you may receive the following error message 

   No reference to array fields without subscript in embedded SQL (1763)
followed by the following error message: 

   Syntax error or access

CAUSE

The driver is returning this error message because of a syntax error in the SQL statement that the database receives.

WORKAROUND

WARNING: Microsoft has not tested the workaround and therefore cannot guarantee its results.

Place a backslash in front of any bracket that contains an array field. For example, the following statement would cause an error 

   SELECT FieldName[1] FROM TableName
where the [1] indicates an element in an array composed of fields. The following line of code works: 

   SELECT FieldName\[1] FROM TableName
in please 

Keywords          : PgmOthr xlquery kbprg kbtool
Version           : 5.0 5.0c
Platform          : WINDOWS

================================================================================

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 2, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.