Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
Tsutomu Ogiwara attributed a sort/ORDER BY failure from MS Access to a known IBM defect (error 309 when linking a table with a unique index and ORDER BY) and advised contacting IBM support. Gary Quiring said IBM still had no fix even in 2.9TC1, while OpenLink and DataDirect drivers worked. Richard Spitz asked whether CSDK 2.90 fixed it. No answer in the thread.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi Muthana.
Probably, you hit the following problem.
167548 ERROR 309 FROM MSACCESS WHEN LINKING A TABLE WITH AN UNIQUE INDEX AND
AN ORDER BY
Contact IBM support.
Regards.
--
Tsutomu Ogiwara from Tokyo Japan.
ICQ#:168106592
>From: <Muthana.AL-Temimi@tu-harburg.hamburg.de>
>To: <informix-list@iiug.org>
>CC: <moltrecht@tuhh.de>
>Subject: sort with access program is not working
>Date: Mon, 7 Feb 2005 16:31:14 +0100
>
>
>Hello there,
>
>I have the following Problem and I need tips to solve my current
>problem.
>I tried separately:
>
>1. CSDK2.81.TC1
>2. CSDK2.81.TC2
>3. CSDK2.81.TC3
>
>and I found that the query with MS-Access program will not work
>correctly and here is the query:
>
>SELECT soshh_lab.mtknr, soshh_lab.pnr
>FROM soshh_lab
>WHERE (((soshh_lab.mtknr)=27255))
>ORDER BY soshh_lab.pnr;>
>And I got the following error:
>
>ODBC-Error
>[Informix][Informix ODBC Driver][Informix]ORDER BY column (pnr) must
>be in select list. (# -309)
>
>I did and tried the same SQL direct into the DB using ISQL --> it works.
>But if I use the same query within MS-Access Program and I alliance my
>table through ODBC. I get always the ERROR just as written above.
>
>I tried the same query but without order by it will be works fine. But
>the sort it will not work. I think my problem is with the CSDK and I
>need to solve this problem.
>
>My environment on Linux Debian:
>
>ISD: 9.30.UC3
>4GL: 7.32.UC2
>ISQL: 7.32.UC2
>
>Can somebody help me on this?
>
>Regards
>Muthana
>
>
sending to informix-list
↪ replying to Tsutomu Ogiwara
Richard Spitz — — source: Usenet: comp.databases.informix
"Tsutomu Ogiwara" <tsutomu_ogiwara@hotmail.com> schrieb:
>Probably, you hit the following problem.
>167548 ERROR 309 FROM MSACCESS WHEN LINKING A TABLE WITH AN UNIQUE INDEX AND
>AN ORDER BY
>
>Contact IBM support.
And what will IBM support do?
I'm asking because we are facing an update from Access 2000/Connect 2.70TC3 to
Access 2003/Connect 2.81TC3 and would like to know in advance what problems to
look forward to.
Regards, Richard
↪ replying to Richard Spitz
Gary Quiring — — source: Usenet: comp.databases.informix
On Tue, 08 Feb 2005 14:09:10 +0100, Richard Spitz
<Richard.Spitz@med.uni-muenchen.de> wrote:
>"Tsutomu Ogiwara" <tsutomu_ogiwara@hotmail.com> schrieb:
>
>>Probably, you hit the following problem.
>>167548 ERROR 309 FROM MSACCESS WHEN LINKING A TABLE WITH AN UNIQUE INDEX AND
>>AN ORDER BY
>>
>>Contact IBM support.
>
>And what will IBM support do?
>
>I'm asking because we are facing an update from Access 2000/Connect 2.70TC3 to
>Access 2003/Connect 2.81TC3 and would like to know in advance what problems to
>look forward to.
>
>Regards, Richard
I have recently contacted IBM about this issue and they still do not have a fix.
The latest version they gave us was 2.9TC1 which is still broken. I have a demo
license from OpenLink and DataDirect that are working fine with MS Access. My
only issue with OpenLink is their drivers are broken if you need to access a 7.x
and 9.x engine in the same query.
Gary Quiring
↪ replying to Gary Quiring
Richard Spitz — — source: Usenet: comp.databases.informix
Gary Quiring <gquiring@msn.com> schrieb:
>>>Probably, you hit the following problem.
>>>167548 ERROR 309 FROM MSACCESS WHEN LINKING A TABLE WITH AN UNIQUE INDEX AND
>>>AN ORDER BY
>>>
>>>Contact IBM support.
>I have recently contacted IBM about this issue and they still do not have a fix.
>The latest version they gave us was 2.9TC1 which is still broken.
What about the recently released version of CSDK 2.90? Is the problem fixed
now, or did anybody receive a patch from IBM support that solves this bug?
Regards, Richard
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.