PDA

View Full Version : Merge Module Contents



wengert
11-25-2002, 09:29 AM
I am unable to see the contents of several merge modules. For example, if I select MDAC2.5 from the redistributals it only shows DCOM95 as a dependency - there is no list of file contents - I also tried Chandima's MM viewer with the same result.

If I look at Jet 3.51 I get a nice list of contained files - not so with Jet 4.0

How can I see all the files contained in a merge module?

Chandima
11-25-2002, 12:03 PM
MDAC, DCOM and Jet merge modules install these files through Custom Actions. These modules simply check minimum system requirements and then launch the microsoft redistributable. The Merge Modules View and viewer I made can only show files that are listed in the msm's File table. You could compare it to a setup you create in Express where you add your program files in the Files View and install Internet Explorer through a Custom Action. We can see the files you added in the Files View, but not the ones in the Custom Action.

For a list of files of MDAC and Jet, see the following URLS:

http://www.microsoft.com/data/MDAC25info/MDAC25SP2Manifest.htm

http://www.microsoft.com/data/MDAC26Info/readmerefresh.htm

http://www.microsoft.com/data/MDAC27Info/en/readmerefresh.htm

http://support.microsoft.com/default.aspx?scid=kb;en-us;Q282010#7

wengert
11-25-2002, 12:44 PM
Thank you Chandima, that is very help[ful. I now see that my problem files are, in fact, included in MDAC2.7 or 2.6. I gather that if I include the MDAC2.7 merge module there is no reason to also include the 2.5 and 2.6 package?

It looks like there are quite a few Windows users who have screwed up mixtures of MDAC installed and I gather that confuses the ISX install process.

I am wondering if I just add the MDAC2.7 microsoft install (the mdac_typ file) as an action at the start of the install, would that solve most of this type of problem. I am amazed at the number of systems where this seems to be an issue. You gotta love Windows <smirk>

Chandima
11-25-2002, 12:55 PM
Yes. There is no reason to include more than one version of MDAC because all you'll end up with is one overwriting the other. MDAC 26 and 27 don't have some files that 25 has (Jet related files).

Is there a problem with using the MDAC 2.7 merge module? If you really want it to install right at the beginning, I have customized MDAC modules that do the normal system requirement checks and install MDAC right at the beginning. If you are interested email me at chandimar@installshield.com and I'll send the one you need.

wengert
11-25-2002, 01:25 PM
Thanks... I will email you for that.

I did remove MDAC2.5 and 2.6 from my project but I notice that when I build, those msms are still being included? Are they dependencies of 2.7?

Chandima
11-25-2002, 01:36 PM
No. MDAC 2.5 is a dependency of DAO 360 and MDAC 2.6 is a dependency of Jet 4.0. Are you using any of these modules? If so, you can use the attached tool to make Jet 4.0 and DAO 360 use the MDAC of your choice (in this case 2.7). This way the build will have just one version of MDAC. You will have to rebuild your project though after making these changes.

The tool will ask for the location of all three MDAC modules, Jet and DAO modules. Then there will be a radio button allowing you to select which version of MDAC you want associated with each. On the last panel, press "Apply" and then "Verify".