On 7/3/07, John Taylor <lists@xxxxxxxxxxxxxxxxxxxx> wrote:


> Yes, that would be superb... but alas, I fear IBM would never do such a
> thing...

Why wouldn't they? What do they have to lose?


They wouldn't simply because they simply won't allow themselves to be
anything near supportive of a Windows effort.

Personally, I'm tired of fighting with the various i5 middleware layers.
ODBC, OLEDB, and now ADO.NET; they always seem to be too far behind in
features and/or fixes. I'm heading towards SQL Server with most new
development projects.

IBM seems to always be dragged kicking and screaming down the Windows
path.
I don't know why. Maybe it's their love affair with Java getting in the
way.
I can't speak for others, but I've developed in Java, and now in .NET. I
choose .NET, and since the i5 team has not made it as easy and productive
to
use DB2/400 with .NET as it is to use SQL Server, I'm voting with my feet.


I too choose .NET for development, but I'm no where near ready to give up on
the iSeries implementation of DB2. I simply love and trust it too much.

I have a couple small projects that I am thinking about moving over to
SQLServer, just to say I have, but for the most part I don't see us leaving
DB2 anytime in the near future.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

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.