Crystal Reports Merge Modules

[Greyeye]

I need help desperately with merge modules for Crystal Reports. This is one of the last things holding up my product launch. I am using .NET 1.1 and the CR that came bundled with VS 2003. I am including the four merge modules that Business Objects says to include - Crystal_Database_Access2003.msm, Crystal_Database_Access2003_enu.msm, Crystal_Managed2003.msm, and Crystal_regwiz2003.msm. I have been including these files and no crystal reports dll files for the full previous three months of beta testing with VS setup projects. It worked fine, no problems at all.

Using IA, the merge modules appear to not be expanding/installing the contents of the msm file on the computers they are installed on. I am including the msm files in the Files screen (where I add all my other files) and adding them to the $TARGETDIR$. I also tried the $COMMONFILES$ directory. In both cases, all four msm files make it into the respective directory but no dll files are pulled out and installed. Is there something special I need to do in the setup of the project? Can somebody give me a walk thru on adding a merge module to a project? Please help me with this...I have done a lot of reading on merge modules and feel like I understand them pretty well but I don't understand what IA is doing differently than my setup projects in VS....Thanks.

Greyeye

[Greyeye]

Ok, I got part of it figured out but not all of it...The part I was missing was that I was adding the merge modules as files instead of merge modules thru the project manager. As a feature request, I would ask that a button be thrown into the file screen for adding merge modules. Anyway, on some computers, its running fine while on one it is giving me an error that indicates that I do not have enough available licenses for CR. I think I can figure that one out outside IA but if anyone has comments on using Orca on the Crystal_regwiz2003.msm file, I would love to hear it...Thanks.

Greyeye