×
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.
Can you explain that one more ?
Are you saying you used the 12.0 drivers, but told the system it was 1.0 ?
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
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 10.0.0.0 (with V5R4) to 12.0.0.0 (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
Programmer/Analyst
Bob Evans Farms, Inc
midrange.com
