Microsoft KB Archive/45979: Difference between revisions

From BetaArchive Wiki
m (Text replacement - "<" to "<")
m (Text replacement - ">" to ">")
 
Line 15: Line 15:
If the field name is not in one of the databases listed in the From clause, then Q+E displays the following error message
If the field name is not in one of the databases listed in the From clause, then Q+E displays the following error message


<pre>  Query field not found <fieldname&gt;
<pre>  Query field not found <fieldname>
</pre>
</pre>
where <fieldname&gt; is the actual field name not found.
where <fieldname> is the actual field name not found.
When using the Order By clause, the field name does not have to be one of the names in the select clause.
When using the Order By clause, the field name does not have to be one of the names in the select clause.
|}
|}

Latest revision as of 10:19, 21 July 2020


SQL Order By Clause Must Be a Field Name in Q+E

Last reviewed: October 31, 1994
Article ID: Q45979

SUMMARY

When using the Order By clause with a SQL select statement, the parameter must be a field name in one of the databases listed in the From clause.

If the field name is not in one of the databases listed in the From clause, then Q+E displays the following error message

   Query field not found <fieldname>

where <fieldname> is the actual field name not found. When using the Order By clause, the field name does not have to be one of the names in the select clause.


KBCategory: kbother

KBSubcategory:

Additional reference words: 2.10


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: October 31, 1994
©1997 Microsoft Corporation. All rights reserved. Legal Notices.