Re: connection string -- SYSTEMIDOTNET

Subject: Re: connection string
From: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
Date: Tue, 19 Jan 2010 12:46:34 -0500
List-archive: <http://archive.midrange.com/systemidotnet>
List-help: <mailto:systemidotnet-request@midrange.com?subject=help>
List-id: ".net use with the System i" <systemidotnet.midrange.com>
List-post: <mailto:systemidotnet@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/systemidotnet>, <mailto:systemidotnet-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/systemidotnet>, <mailto:systemidotnet-request@midrange.com?subject=unsubscribe>

The IBMDA400 is part of client access. I did not want to load client
access on every PC that would go to the 400.

You'd only need client access on the web _server_. The clients aren't
taking to the iSeries, they're taking to the web server, only the web
server is talking to the iSeries.

Isn't there a plain old ODBC that I could use?

Nope. The ODBC "driver" is specific to the database you're connecting
to. Just like the .Net driver for iSeries, there's an ODBC driver for
iSeries. But again, it doesn't matter, The "client" isn't talking to the
iSeries, only the server is.

-Walden

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: connection string , SirJohn
Re: connection string , SirJohn

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