Received: from u1.abs.net (root@u1.abs.net [207.114.0.131]) by hub.org (8.8.8/8.7.5) with ESMTP id UAA06032 for ; Sat, 9 May 1998 20:45:09 -0400 (EDT) Received: from insightdist.com (nobody@localhost) by u1.abs.net (8.8.5/8.8.5(+AntiRelay)) with UUCP id UAA02548 for pgsql-interfaces@postgreSQL.org; Sat, 9 May 1998 20:30:00 -0400 (EDT) X-Authentication-Warning: u1.abs.net: nobody set sender to insightdist.com!byronn using -f Received: from ceodev by insightdist.com (AIX 3.2/UCB 5.64/4.03) id AA18137; Sat, 9 May 1998 20:19:27 -0400 Received: from ppp0_ceodev by ceodev (AIX 4.1/UCB 5.64/4.03) id AA24654; Sat, 9 May 1998 20:19:25 -0400 Message-Id: <3554F0E4.AB657CA1@insightdist.com> Date: Sat, 09 May 1998 20:12:21 -0400 From: Byron Nikolaidis X-Mailer: Mozilla 4.05 [en] (Win95; I) Mime-Version: 1.0 To: Chris Osborn Cc: pgsql-interfaces@postgresql.org Subject: Re: [INTERFACES] NEW ODBC DRIVER References: <35533446.92762625@insightdist.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Access insists on using order by clauses like that, even though the driver returns information saying it can't support it! Postgres simply can't handle order by clauses without the fields also being in the target. The error you see is a legitimate error coming from the backend. When the backend can handle those kinds of order by clauses, the error will stop happening. Byron Chris Osborn wrote: > I just downloaded it, and I cannot get any queries that have an > "ORDER BY" in them to work. Access '97 keeps returning an ODBC call > failed error, and gives me the message: > > ERROR: The field being ordered must appear in the target list (#1) > > If I cut and paste the SQL code directly into a psql session, it > runs just fine. > > --- > Chris Osborn, Network Administrator T3West/WebCow! > 707 255 9330 x225 - Voice 1804 Soscol Ave, #203 > 707 224 9916 - Fax Napa, CA 94559 >