ODBC Fields Order -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

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!

Dave Shaw
Spartan International, Inc.
Spartanburg, SC
+---
| 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 mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.