Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations John Tel on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

What are merge modules?

Status
Not open for further replies.

ZK

MIS
Oct 2, 2000
27
GB
Hi

As you may have guessed, I am a beginner to MSI packaging. I am currently having a problem packaging Visio 2000 and another FTP client program, both of which use VBA.

On packaging each of the applications, both asked if I wanted to use certain merge modules, which appeared to be related to VBA files.

I selected no, and they continued on being packaged.

Now I have a problem. If the Visio MSI is installed WITHOUT the FTP program being installed, it works fine. But the moment I execute the FTP MSI, Visio refuses to open, and asks for the VBA CD.

So this is why I think I should've selected Yes to the initial packaging process, when it asked me if I wanted to use the merge modules.

Can anyone confirm if my assumption is correct? Or am I barking up the wrong tree?

Is this why merge modules are used? What are the advantages of using, for example, VBA merge modules?

Thanks a lot
ZK
 
Seeing as how your message is dated March 6, I hope you are still not having the same issue. However, if you are still having the same issue this might be a possible way to fix the problem:

I scripted Vision 2000 for our company and found a similar issue. The Visio CD contained a VBA.msi file which I had to include in my installation. Basically, I built a Wise InstallManager 1.5 wrapper executable that launched both the Visio2K.msi and the VBA.msi. I found that I needed the VBA.msi file otherwise Visio would hang when it was launched. Aside from the standard Office 2000 requirement for Visio users, nothing else but the VBA.msi was required.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top