Client Access ODBCs' -- 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.

Subject: Client Access ODBCs'
From: "JR VanOoteghem" <jr@xxxxxxxxx>
Date: Fri, 30 Sep 2005 15:45:42 -0400
List-archive: <http://archive.midrange.com/midrange-l>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Hello,

            I've created an ASP page on my webserver that extracts
particular fields out of our database on the Iseries. Problem is, I keep
getting "data provider could not be initialized" when opening the page. I'm
on V5R3 on the 400 and Client access as well. I've done the usual updating
MDAC and JET as well as reinstalling the Iseries ODBC's. The DSN tests out
fine so I don't know where to go from here. Any help is appreciated.

 

 

JR VanOoteghem

As an Amazon Associate we earn from qualifying purchases.

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.