This stuff:

Needed because installing the 6.1 driver replaces the 5.x driver.

Craig Pelkie

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen
Sent: Thursday, March 29, 2012 2:00 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: .NET application iSeries Access requirement???

Can you explain that one more ?

Are you saying you used the 12.0 drivers, but told the system it was 1.0 ?

Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business
Email: richard@xxxxxxxxxxxxxxx
Web Site:
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT


message: 1
date: Thu, 29 Mar 2012 20:46:52 +0000
from: "Maassel, John R." <John_Maassel@xxxxxxxxxxxx>
subject: RE: .NET application iSeries Access requirement???

A problem we've run into when we started our migration to Client Access 6.1
is that the version of the IBM.Data.DB2.iSeries assembly went from
(with V5R4) to (with V6R1). We immediately started getting messages
complaining about not finding the right version of IBM.Data.DB2.iSeries.
After we tracked it down to the new version of Client Access, we found that
we'd either have to recompile all of the .NET objects that use the database
against the new version, or put in binding redirects in the machine.config
file. Since we are in a mixed environment, we just set up the binding
overrides to make everything pretend it's on 5.4's driver.

John Maassel
Bob Evans Farms, Inc

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at

This thread ...


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

This mailing list archive is Copyright 1997-2020 by 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].