Merge Modules and moving from InstallAware 3

Got a problem you cannot solve? Try here.
Post Reply
[MS]Mark
Posts: 39
Joined: Mon Dec 06, 2004 9:11 am
Location: UK

Merge Modules and moving from InstallAware 3

Post by [MS]Mark »

Just upgraded to InstallAware 5 Admin Studio from InstallAware 3 Enterprise - having problems with existing projects that use MSM Modules (namely VFPODBC and Crystal Reports).

When I build the project I get the an error:
Created Windows Installer database
Error during build: Unable to merge Windows Installer database with module vfpodbc
If I create a new project exactly the same it works OK. Obviously, I don't fancy doing this as I have ~15 Projects which use Merge Modules...is there anyway of resolving this error easily?
jimo
Posts: 342
Joined: Fri Aug 19, 2005 10:59 am
Location: Atlanta, GA
Contact:

Post by jimo »

You may want to try opening the project removing the VFPODBC merge module, save the project, re-add the merge module, save then try building.
Jim Oswell
Software Engineering Manager, Dental
Greenway Health, LLC
http://greenwaymedical.com
[MS]Mark
Posts: 39
Joined: Mon Dec 06, 2004 9:11 am
Location: UK

Post by [MS]Mark »

jimo wrote:You may want to try opening the project removing the VFPODBC merge module, save the project, re-add the merge module, save then try building.
Still the same error if I do that...
jimo
Posts: 342
Joined: Fri Aug 19, 2005 10:59 am
Location: Atlanta, GA
Contact:

Post by jimo »

Mark,

I personally have migrated ALL my VFP merge modules to include scripts.

This is very easy to do with IA, under the tools menu select Database Import Wizard and point it to the vfpodc.msm file and you have an include script.

I have found that this allows for more flexibility, I can conditionally include the include scripts in a Web Media Block so if the vfpodbc drivers are already installed on the target machine the install package does not download them and thus my install package is smaller and faster.
Jim Oswell
Software Engineering Manager, Dental
Greenway Health, LLC
http://greenwaymedical.com
[MS]Mark
Posts: 39
Joined: Mon Dec 06, 2004 9:11 am
Location: UK

Post by [MS]Mark »

Thanks - I'll have a look at that :)
MichaelNesmith
Posts: 3452
Joined: Thu Dec 22, 2005 7:17 pm
Contact:

Post by MichaelNesmith »

It should also work if you delete the merge module reference, delete the file on disk (in your project folder), and then re-add it. This would be the same as starting a new empty project with which you say it works.
Michael Nesmith
Install[b]Aware[/b]
[i]Home of The Next Generation MSI Installer[/i]
Get your free copy today - http://www.installaware.com/
dunion
Posts: 106
Joined: Tue Oct 14, 2008 10:43 am

Did you ever get this resolved? I'm seeing this with all...

Post by dunion »

Seems like it must be a system change: same project used to work, now I get this for all merge modules. The only thing I've done on the system lately related to MSI is install 'Orca' to look at merge modules. Could that have effected something?

I"ve tried removing and re-adding the merge module and it isn't specific to any given merge module.
Post Reply