Re: Java vs .NET was: RPGIII compiler vs Visual Basic

On Tue, 2005-06-21 at 17:46, midrange-l-request@xxxxxxxxxxxx wrote:
> date: Tue, 21 Jun 2005 13:30:58 -0400
> from: "Walden H. Leverich" <WaldenL@xxxxxxxxxxxxxxx>
> subject: RE: Java vs .NET was: RPGIII compiler vs Visual Basic
> 
> >The difference is that in JDBC the driver is a string: in 
> >.NET you have to actually code for the particular class. 
> 
> No you don't (have to code). The following is completely soft-coded.
> Change entries in App.Config and you move from iSeries.NET driver to
> Oracle to OLEDB. And if you upcast the connection you can use
> type-specific methods and properties (See the use of JobName below).
> Obviously if you upcast you're responsible for making sure it's a valid
> upcast, you can't case a SqlConnection to an iDB2Connection.

Walden,

As usual, you are correct: I didn't mean to imply it can't be
soft-coded, I was just trying to point out that in JDBC you use a
different string, in .NET you use a different class (and the string in
JDBC is simply a reference to a different driver class).  Yes, you can
absolutely soft-code: that's why iHOC works the way it does, the
connections are all softcoded in the program and then executed
dynamically based on user selection.

Joel