Informix -309 Error and Access Sorting
Hi, I keep on encountering a problem with the Informix Client SDK library (All Versions) MS Access cannot sort using this ODBC driver (except it seems to sort ok on keys). Is there any way to fix this. I'm currently using Informix CLient SDK 2.6 and 2.3, with MS Access 97 (I think it happens on 2000 as well, although not sure). Cheers Miles Roper
Miles Roper wrote:
>
> Hi,
>
> I keep on encountering a problem with the Informix Client SDK library
> (All Versions) MS Access cannot sort using this ODBC driver (except it
> seems to sort ok on keys). Is there any way to fix this.
>
> I'm currently using Informix CLient SDK 2.6 and 2.3, with MS Access 97
> (I think it happens on 2000 as well, although not sure).
>
> Cheers
>
> Miles Roper
# finderr 309
-309 ORDER BY column column-name must be in SELECT list.
The indicated column appears in the ORDER BY clause of this SELECT, but
it is not in the select list (the list of values that follows the word
SELECT). This action is not supported. All sort keys must be present in
the output rows in order to sort. Revise the statement to follow this
rule. If you want to sort only on an expression that involves this
column, not on the column itself, refer to the expression by the number
of its position in the select list.
Clearly, M$ Access is not producing SQL that consistently follows this
rule. Try and capture the statement that is causing the problem using
'onstat -g ses' when it occurs.
Brett Randall
<!doctype html public "-//w3c//dtd html 4.0 transitional//en">
<html>
Hi Brett,
<p>Don't seem to have a "onstat" program. Is it part of informix-se
(we have se not on-line)? Or part of the Client SDK Pak? In
either case I cannot find it.
<p>Cheers
<p>Miles
<p>Brett Randall wrote:
<blockquote TYPE=CITE>Miles Roper wrote:
<br>>
<br>> Hi,
<br>>
<br>> I keep on encountering a problem with the Informix Client SDK library
<br>> (All Versions) MS Access cannot sort using this ODBC driver (except
it
<br>> seems to sort ok on keys). Is there any way to fix this.
<br>>
<br>> I'm currently using Informix CLient SDK 2.6 and 2.3, with MS Access
97
<br>> (I think it happens on 2000 as well, although not sure).
<br>>
<br>> Cheers
<br>>
<br>> Miles Roper
<p># finderr 309
<br>-309 ORDER BY column column-name must be in SELECT
list.
<p>The indicated column appears in the ORDER BY clause of this SELECT,
but
<br>it is not in the select list (the list of values that follows the word
<br>SELECT). This action is not supported. All sort keys must be present
in
<br>the output rows in order to sort. Revise the statement to follow this
<br>rule. If you want to sort only on an expression that involves this
<br>column, not on the column itself, refer to the expression by the number
<br>of its position in the select list.
<p>Clearly, M$ Access is not producing SQL that consistently follows this
<br>rule. Try and capture the statement that is causing the problem
using
<br>'onstat -g ses' when it occurs.
<p>Brett Randall</blockquote>
</html>
Miles Roper wrote:
>
> Hi Brett,
>
> Don't seem to have a "onstat" program. Is it part of informix-se
No, part of OnLine/IDS. Not in SE AFAIK.
> (we
> have se not on-line)? Or part of the Client SDK Pak? In either case
> I cannot find it.
>
> Cheers
>
> Miles
>
> Brett Randall wrote:
>
> > Miles Roper wrote:
> > >
> > > Hi,
> > >
> > > I keep on encountering a problem with the Informix Client SDK
> > library
> > > (All Versions) MS Access cannot sort using this ODBC driver
> > (except it
> > > seems to sort ok on keys). Is there any way to fix this.
> > >
> > > I'm currently using Informix CLient SDK 2.6 and 2.3, with MS
> > Access 97
> > > (I think it happens on 2000 as well, although not sure).
> > >
> > > Cheers
> > >
> > > Miles Roper
> >
> > # finderr 309
> > -309 ORDER BY column column-name must be in SELECT list.
> >
> > The indicated column appears in the ORDER BY clause of this SELECT,
> > but
> > it is not in the select list (the list of values that follows the
> > word
> > SELECT). This action is not supported. All sort keys must be present
> > in
> > the output rows in order to sort. Revise the statement to follow
> > this
> > rule. If you want to sort only on an expression that involves this
> > column, not on the column itself, refer to the expression by the
> > number
> > of its position in the select list.
> >
> > Clearly, M$ Access is not producing SQL that consistently follows
> > this
> > rule. Try and capture the statement that is causing the problem
> > using
> > 'onstat -g ses' when it occurs.
> >
> > Brett Randall
Thanks *so* much for posting in HTML. It makes everyone's life so much richer.
In the year of Our Lord Tue, 30 Jan 2001 08:55:49 +1300, Miles Roper
<mroper@coasthealth.co.nz> spake, saying:
><!doctype html public "-//w3c//dtd html 4.0 transitional//en">
><html>
>Hi Brett,
><p>Don't seem to have a "onstat" program. Is it part of informix-se
>(we have se not on-line)? Or part of the Client SDK Pak? In
>either case I cannot find it.
><p>Cheers
><p>Miles
><p>Brett Randall wrote:
><blockquote TYPE=CITE>Miles Roper wrote:
><br>>
><br>> Hi,
><br>>
><br>> I keep on encountering a problem with the Informix Client SDK library
><br>> (All Versions) MS Access cannot sort using this ODBC driver (except
>it
><br>> seems to sort ok on keys). Is there any way to fix this.
><br>>
><br>> I'm currently using Informix CLient SDK 2.6 and 2.3, with MS Access
>97
><br>> (I think it happens on 2000 as well, although not sure).
><br>>
><br>> Cheers
><br>>
><br>> Miles Roper
><p># finderr 309
><br>-309 ORDER BY column column-name must be in SELECT
>list.
><p>The indicated column appears in the ORDER BY clause of this SELECT,
>but
><br>it is not in the select list (the list of values that follows the word
><br>SELECT). This action is not supported. All sort keys must be present
>in
><br>the output rows in order to sort. Revise the statement to follow this
><br>rule. If you want to sort only on an expression that involves this
><br>column, not on the column itself, refer to the expression by the number
><br>of its position in the select list.
><p>Clearly, M$ Access is not producing SQL that consistently follows this
><br>rule. Try and capture the statement that is causing the problem
>using
><br>'onstat -g ses' when it occurs.
><p>Brett Randall</blockquote>
></html>
>