RE: ODBC Fields Order

You may want to try 

SELECT * FROM QSYS2/SYSCOLUMNS WHERE TABLE_NAME = 'tablename' 

for each table and compare the results.  May show you something.

Hope it helps!

JN

-----Original Message-----
From: Shaw, David [mailto:dshaw@spartan.com]
Sent: Friday, March 10, 2000 12:25 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: ODBC Fields Order


SELECT * from STRSQL on the /400 shows the fields in the correct order in
both
cases.  SELECT * from MS Query (which is what I have on this PC) through
ODBC
shows the correct order for the original, but a different order (not
alphabetic
- it appears to be random, I can't see a pattern) for the copy.  SELECT *
through the ODBC tools that our cross-platform developers are using does the
same as MS Query.  I'm thinking it's not the tools, but rather something
about
either the Client Access ODBC driver or the way the /400 loads the system
catalogs when CRTDUPOBJ is used to create a file.  We're also using
different
versions of the ODBC driver - I'm running Client Access Express V4R4 with
the
latest service pack, and the lady who detected it first is running CA for
95/NT
V3R1M3 with a service pack from sometime in 1998.  OY!

> -----Original Message-----
> From: Rob Berendt [mailto:rob@dekko.com]
> 
> I saw 'SELECT * through ODBC from the copy'.  I also saw 
> 'SELECT * of the original'.  My question is this.  Were 
> both selects done using ODBC, or just the first?  If you 
> do both selects using STRSQL what field order do you get?  
> What I am getting to is this, is it possible that your 
> ODBC tool does something weird like put the fields in 
> alphabetic order before presenting them?  Regardless of 
> how the file was created:  DDS, SQL, ODBC SQL, or whatever;
> CRTDUPOBJ will NOT reorder fields.
> 
> 
> 
> 
> dshaw@spartan.com on 03/10/2000 11:12:29 AM
> Please respond to MIDRANGE-L@midrange.com@Internet
> To:   MIDRANGE-L@midrange.com@Internet
> cc:    
> Fax to:       
> Subject:      ODBC Fields Order
> 
> We have a file which was created by an SQL statement sent 
> through ODBC to the
> /400.  When I create a copy of it using CRTDUPOBJ, everything 
> looks fine from
> the /400, however if I do a SELECT * through ODBC from the 
> copy, the fields are
> all out of sequence.  If I do the SELECT * of the original, 
> the fields are in
> the correct sequence, the same DSPFFD or SQL on the /400 
> shows them.  Maybe I'm
> blind, but I can't find any documentation saying that this 
> might occur.  I'm
> told that this was first seen at V4R2, but I wasn't here 
> then.  We're at V4R4
> now.  Does anyone have any idea why this might be?  Thanks!
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---