mdac2.7 on windows 2003

When installing on windows 2003, and mdac2.7 or mdac2.6 merge module included in the setup, an error message appears that mdac does not support the OS.

I know that mdac is by default installed on the 2003 OS. But still is there a work awound to this check.

The following is the message that I recieve:

The minimum supported configuration for installing MDAC 2.7 requires one of the following:

Microsoft Windows 98 with Y2K Update 2 and Internet Explorer 4.01 SP2 or later

Microsoft Windows 98 Second Edition

Microsoft Windows Millennium

Microsoft NT® 4 SP5 (or greater) and Internet Explorer 4.01 SP2 or later

Microsoft Windows 2000


Thanks,
Rony.

[Stefan Krueger]

This is a bug in the merge module. The source can be found in the InstallShield objects directory. Here's a quote from the .vbs file:

ElseIf (vVerNT = "501") Then
' If it is XP do not install
Else
Session.Property("OS_NOTSUPPORTED")="1"
End If

I believe this should be changed to:

ElseIf (vVerNT >= "501") Then

You can open the module source in Developer and build a fixed module yourself.

[Chandima]

This has already been fixed. The updated merge modules (both MDAC 2.6 and 2.7) are in the Developer merge module gallery . These modules shipped with Service Pack 1 for Developer 8.0 and Express 4.0. Thanks!

[Stefan Krueger]

Oh, you're right. I have SP1+2 installed but still have the old mdac module. But in the gallery there's a fixed module (and it's listed in tools -> check for updates)

In the new module there is:

ElseIf ((vVerNT = "501") Or (vVerNT = "502")) Then

which means that this will fail again on the next version of Windows. Wouldn't it be saver to assume that future Windows versions include the latest mdac version?
And if a current MDAC version is detected, I think there shouldn't be an error message.

[Chandima]

I totally agree. We are planning on updating both MDAC 2.6 and 2.7 to work without the use of any VBScript Custom actions. The MDAC 2.5 module works this way.