Very Computer

We are being asked to upgrade from MDAC 2.1 to 2.5 on our web server.  After
the headaches we experienced after upgrading to version 2.1 we are really
reluctant to make this upgrade without hearing from others.

Any positivie or negative experiences from those who have upgraded would
really be appreciated.

Thanks,

John

Well,

ADO 2.5 itself is very compatible. I only found out on 'some' systems that
IIS does not start anymore and ends up with the 'out of resources'
inetinfo.exe error.

This error in fact did not have to do _-> anything <- with RAM because I
have really sufficient RAM.

The error started after I upgraded to 2.5. It happened on engines that also
had RDO installed (remote data objects) and a copy of the Visual Basic 6.0
runtime.

Strange is that I seem to be the only whiner about this with ADO 2.5...

You can make a backup of your system before upgrading and if it works at
once (IIS starts) you are safe.

Regards,

Quote:> We are being asked to upgrade from MDAC 2.1 to 2.5 on our web server.
After
> the headaches we experienced after upgrading to version 2.1 we are really
> reluctant to make this upgrade without hearing from others.

> Any positivie or negative experiences from those who have upgraded would
> really be appreciated.

> Thanks,

> John

You may find some apps don't work anymore.

It is not totally backward compatible. I developed a db app using v2.0 and
it would not work on a test machine that had v2.5 installed. I discovered
that they had changed the "reference IDs"

For example where i v2.0 SomeMethod() called
 InvokeHelper(0x1, ....);

in v2.5 it need to call
 InvokeHelper(0x2, ....);

I have seen a few posts in this ng where people had problems with this.

Quote:> We are being asked to upgrade from MDAC 2.1 to 2.5 on our web
server.  After
> the headaches we experienced after upgrading to version 2.1 we are
really
> reluctant to make this upgrade without hearing from others.

> Any positivie or negative experiences from those who have upgraded
would
> really be appreciated.

In an application I'm developing the following works under 2.1, but
not under 2.5.

I have an ADO disconnected recordset, which includes the following
rows in its 14,000 rows:

Col1(Integer)    Col2(VarChar(50))    Col3(Bit)
20070               English 2                   0
20071               English 3                   0
20170               Maths 2                     0
20171               Maths 3                     0
20172               Maths 4                     0

MyRs.Filter="Col1 >= 20170 AND Col3 = 0"
returns 3 records under v2.1, and 0 records under v2.5
MyRs.Filter="Col2 Like '%ath%' AND Col3 = 0"                   returns
3 records under both versions

At my company we have an SQL 7 app that uses Access for some temp
databases on client machines.  After upgrading from 2.1 to 2.5, we can
no longer set defaults on fields in tables in the Access db.

I also had another strange problem where my right-click pop-up in
Explorer lost the 'New Microsoft Data Link File' entry after I
installed the upgrade.

Quote:> We are being asked to upgrade from MDAC 2.1 to 2.5 on our web
server.  After
> the headaches we experienced after upgrading to version 2.1 we are
really
> reluctant to make this upgrade without hearing from others.

> Any positivie or negative experiences from those who have upgraded
would
> really be appreciated.

> Thanks,

> John

Sent via Deja.com http://www.deja.com/
Before you buy.

I probably speak for many silent lurkers...

I'm running Windows NT 4.0. I generally keep my system up to date with the
newest service packs, patches, etc. Installing MDAC 2.5 was a breeze. My C++
and VB applications compiled and ran as they did before.

Brian Oraas
Albacore Research, Ltd.

About the right click which lost the "Ms Data Link..." stuff, it is written
in the doc that with the new MDAC2.5 it will not be anymore accessible by a
right click just because you simply have to select in this right click "Text
document" which will create a "new document.txt" and rename it into "new
document.udl" and you got the same :)

After updating to ADO 2.5 by the way everything is still working perfectly,
and it seems that some feature that were not working porperly (in the event
stuff) before are working now much better!

--

---
Jean-Christophe Berthon
Nttrufr?eistofnun slands
(Icelandic Institute of Natural History)

Or you can restore the New/MS Data Link by adding this to your registry:

Windows Registry Editor Version 5.00

"Data"=hex:ff,fe,5b,00,6f,00,6c,00,65,00,64,00,62,00,5d,00,0d,00,0a,00,3b,00
,\

20,00,45,00,76,00,65,00,72,00,79,00,74,00,68,00,69,00,6e,00,67,00,20,00,61,\

00,66,00,74,00,65,00,72,00,20,00,74,00,68,00,69,00,73,00,20,00,6c,00,69,00,\

6e,00,65,00,20,00,69,00,73,00,20,00,61,00,6e,00,20,00,4f,00,4c,00,45,00,20,\

00,44,00,42,00,20,00,69,00,6e,00,69,00,74,00,73,00,74,00,72,00,69,00,6e,00,\

67,00,0d,00,0a,00,50,00,52,00,4f,00,56,00,49,00,44,00,45,00,52,00,3d,00,6d,\
  00,73,00,64,00,61,00,73,00,71,00,6c,00,3b,00,0d,00,0a,00

I've done this on my Win2K boxes and it works quite well.

We had server crashes in high-traffic conditions with 2.1 and
a mostly ASP/ADO site.  We could not find a specific bug and
our application worked fine in low/medium traffic conditions.
Memory was not low.   We had 512 MB installed and less than 128 MB
were consumed when it crashed.  Upgrading to Win2K with MDAC 2.5
made the crashes go away.  Testing this on NT4 with MDAC 2.5 appeared
to have fixed the problem but we did not try it in production.
We are now sticking with Win2K (which has MDAC 2.5 pre-installed).
Norm

Quote:> We are being asked to upgrade from MDAC 2.1 to 2.5 on our web
server.  After
> the headaches we experienced after upgrading to version 2.1 we are
really
> reluctant to make this upgrade without hearing from others.

> Any positivie or negative experiences from those who have upgraded
would
> really be appreciated.

> Thanks,

> John

Sent via Deja.com http://www.deja.com/
Before you buy.