Re: EXCSQLSTM command: Keyword ORDER not expected. Valid tokens: ) UNIONEXCEPT. -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: EXCSQLSTM command: Keyword ORDER not expected. Valid tokens: ) UNIONEXCEPT.
From: Joe Pluta <joepluta@xxxxxxxxxxxxxxxxx>
Date: Thu, 10 Apr 2008 10:18:21 -0500
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Peter Vidal wrote:

... I have to say Eric that when I run the SQL with ORDER BY ITNBR, I have the error on the SELECT clause but when I change it to be ORDER BY 3, the select clause runs OK...

"ORDER BY ITEM" should work. The column name for the CASE statement is ITEM, not ITNBR.

Joe

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.