RESULT: Problem with dbaccess and dbschema

Message is sent with MIME. Attachments are base64 encoded --TFS-with-MIME-and-DIME Content-Type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: quoted-printable Aha, =20 Mark Stock mentioned that this was a dbaccess bug and that it would be= =20 fixed shortly, so I got a copy of 7=2E22 loaded yesterday, checked the= =20 release notes and lo and behold, in the "bugs yet to be fixed" bit: =20 57011 DBACCESS INFO SQL STATEMENT SHOWS COLUMNS IN INCORRECT ORDER AND ALSO SHOWS WRONG COLUMN IN INDEX =20 It appears that dbaccess doesn't do the order by=2E =20 Ta Davin ********************************************************************** DST International Tel:+44 181 390 5000 www=2Edstinternational=2Eco=2Eu= k=20 This message and any attachments to it is intended only for the=20 individual or company to which it is addressed and may contain=20 information which is privileged, confidential or prohibited from=20 disclosure or unauthorised use=2E If the recipient of this=20 transmission is not the intended recipient, or the employee or agent=20 responsible for delivering such materials to the intended recipient,=20 you are hereby notified that any use, any form of reproduction,=20 dissemination, copying, disclosure, modification, distribution and/or=20 publication of this e-mail message or its attachments other than by=20 its intended recipient is strictly prohibited by the sender=2E =20 If you have received it in error, please notify us immediately by=20 telephone on the number above and destroy the message and all copies=20 in your possession=2E ********************************************************************** --TFS-with-MIME-and-DIME Content-Type: text/rtf; name="MSGCC.RTF" Content-transfer-encoding: base64 {\\rtf1\\ansi \\deff0\\deflang1024{\\fonttbl{\\f0\\froman Tms Rmn;}{\\f1\\froman Symbol;}{\\f2\\fswiss Helv;}} {\\colortbl;\\red0\\green0\\blue127;\\red0\\green127\\blue0;\\red0\\green127\\blue127;\\red127\\green0\\blue0; \\red127\\green0\\blue127;\\red127\\green127\\blue0;\\red127\\green127\\blue127;;\\red0\\green0\\blue255; \\red0\\green255\\blue0;\\red0\\green255\\blue255;\\red255\\green0\\blue0;\\red255\\green0\\blue255; \\red255\\green255\\blue0;\\red255\\green255\\blue255;}\\paperw12240\\paperh15840\\margl1800\\margr1800\\margt1440\\margb1440 \\gutter0 \\defformat\\sectd \\pard\\plain {\\plain \\f0 \\cb7 \\cf0 \\cb1 \\cf14 \\cb1 \\cf14 Aha,\\ \\cb1 \\cf14 \\ \\cb1 \\cf14 \\cb1 \\cf14 Mark Stock mentioned that this was a dbaccess bug and that it would be \\ \\cb1 \\cf14 \\cb1 \\cf14 fixed shortly, so I got a copy of 7.22 loaded yesterday, checked the \\ \\cb1 \\cf14 \\cb1 \\cf14 release notes and lo and behold, in the "bugs yet to be fixed" bit:\\ \\cb1 \\cf14 \\ \\cb1 \\cf14 \\cb1 \\cf14 57011 DBACCESS INFO SQL STATEMENT SHOWS COLUMNS IN INCORRECT\\ \\cb1 \\cf14 \\cb1 \\cf14 ORDER AND ALSO SHOWS WRONG COLUMN IN INDEX\\ \\cb1 \\cf14 \\ \\cb1 \\cf14 \\cb1 \\cf14 It appears that dbaccess doesn't do the order by.\\ \\cb1 \\cf14 \\ \\cb1 \\cf14 \\cb1 \\cf14 Ta\\ \\cb1 \\cf14 \\cb1 \\cf14 Davin\\ \\par }} --TFS-with-MIME-and-DIME--