× 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.


  • Subject: RE: Rumba ODBC bug?
  • From: "Shaw, David" <dshaw@xxxxxxxxxxx>
  • Date: Mon, 12 Jun 2000 10:02:50 -0400

> -----Original Message-----
> From: Bale, Dan [mailto:DBale@lear.com]
> 
> We are a Rumba 2000 shop.  We are using Rumba's "optimized" 
> ODBC to download
> AS/400 files directly into MS Access97.  (FWIW, we're also 
> running on NT4.)
> 
> A new table is created in Access by using ODBC.  The data is being
> downloaded into Access.  Everything looks good, EXCEPT that, 
> intermittently
> (but more and more often now), the sequence of the fields in 
> the Access
> table is not the same as in the AS/400 file.  This is driving 
> us nuts.  (I
> am aware of how to manipulate the field sequence in an Access 
> table via the
> Design sheet, but I don't want / shouldn't have to do this!)
> 
> Usually, the pattern is that the first 'n' columns/fields 
> will be shifted
> several columns over; it could be the first one column/field 
> or the first
> seven (or anything in between).
> 
> The driver is called "RUMBA AS/400 Optimized Server (32bit)", 
> the version is
> 1502.05.00.00, the file name is WDODBCOS.DLL, and the date is 
> 10/5/99.  fwiw
> 
> Has ANYBODY run into this problem?  

This also occurs with the Client Access ODBC drivers, all versions.  It
sounds like Rumba must be using the same system catalogs on the /400 that
Client Access uses.  The ODBC specifications do not define what order the
fields should be presented in (thanks so much for that, Micro$oft!), so for
performance reasons IBM presents them in relative record number order.  The
catch is that the file in which this particular information is stored is
defined with REUSEDLT(*YES), so RRN order frequently doesn't match field
position order.  Chuck Pence in DB2 development in Rochester has a fairly
involved work-around that effectively adds the field position to the index
of the system catalog file.  I don't believe I've ever seen him on this
list, but he is on the comp.sys.ibm.as400.misc newsgroup frequently, if you
want to contact him about it, or you can try e-mailing him at
crp@us.ibm.com.  He asks that we users not redistribute the instructions
among ourselves, so please don't ask me to forward them to you.

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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.