I have a problem, in that, Relius Government Forms 5500 Forms must update some of the MDAC dlls (version 2.8)...even with Merge Modules. When the installer runs, I get an error 1931, 1991, and 1904, on three separate DLLs. Some quick Google searches tell me that this isn't uncommon for MDAC DLLs, but the some of the solutions are a bit hard for me to grasp.

My question is, how do I create a custom action that checks the version of the MDAC and installs it before the MSI installs? I'm using Wise Package Studio 6 and have only been packaging apps for a few months.

Any and all suggestions would be appreciated.
1 Comment   [ - ] Hide Comment


  • Hi Jmelton,
    How did you manage to package the application. Did u repackaed the application using MSI, or used the response file. I want to know how you performed silent installation and uninstallation, because I am unable to get through this application. Kindly help!!!
Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
Answer this question or Comment on this question for clarity


divide and conquer. install mdac before the app.
Answered 02/02/2007 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
Thanks for you response and sorry it took so long to reply back.

I figured out how to launch the MDAC install via a Custom Action in Execute Immediate. I have a couple of additional problems that I'm not sure how to deal with.

1. As it stands, the MDAC will try to install no matter what the current MDAC version is. I have tried to put the CA inside and IF statement based on a Reg Search I have built in. So far, the CA either doesn't run, or it runs every time. This, in and of itself isn't too bad, but it kind of feels like a brute force method of pounding a square peg into a round hole. Any suggestions would be greatly appreciated.

2. When this app is uninstalled, the MDAC also uninstalls...which is pretty much the end of ALL data access on that PC. I have been scouring the web looking for how to prevent this, but no luck so far.

The specific CA I am using is Execute Program from Installation.
Answered 02/09/2007 by: JMelton
Senior Yellow Belt

Please log in to comment

I suggest that you split bundle packages, my point of view is it's not so good install packages with (mdac or any other component) that can be installed by another application. Maybe you can handle it as (core system package) and install it alone. I think it's easier to support than control list of applications that install MDAC or this kind of component.

Answered 02/27/2007 by: bobcapilontra
Senior Yellow Belt

Please log in to comment
Thanks for the reply. I actually found an article at http://support.microsoft.com/default.aspx?scid=kb;en-us;320788 (based on a Related Link in the MDAC package at http://itninja.com/link/"how-to-install-mdac-with-a-windows-installer-merge-module"-white-paper-is-available
) on how to update the existing MDACTYP merge module using Orca.

It was actually quite painless and resolved this particular issue. The Custom Action ended up causing far more problems that it was worth.

Thanks again!
Answered 03/07/2007 by: JMelton
Senior Yellow Belt

Please log in to comment