>I think you need only to install latest Application Development Client
8.2.x to get Development Add-In and DB2 provider for .NET (which was
greatly enhanced in 8.2) -- if client in not on the same machine as DB2
server.
This is our case. I'm going to try this.
You can install DB2 ADC directly from the latest fixpak.
I am not sure of the significance of this.
If you are accessing DB2 with ODBC or OLE DB providers you don't have
to change anything (slower than DB2 .NET provider).
Curerently, we're using ODBC. But it's noticeably slow. The DB2 client
is much faster when showing data (and minimizing the screen to avoid
printout slowdown). So, as we are moving to .NET and rewritting a bunch
of things, we'd like to get the best solution for the DB connection as
well.
Personally I would be staying with higher fixpak level. It is always a
tradeoff between well known bugs and unknown bugs. But in case of any
malfunctions you probably will be guided by tech support to higher your
db2 level -- for you this means "forced migration". It easier to plan
it, but anyway going up from 8.1.6 is quite straightforward.
We have a plan to upgrade soon around the time we do a server migration
which is being planned. It is a bit more complex to get an upgrade on
the server, which requires an upgrade to the production server as well,
so we'd rather wait for the planned one. Same is true with fixpacks,
but those are obviously easier. Therefore, we're just going to upgrade
the local client for now.
Thanx for the reply. I appreciate it.
B.
