Posted 02 December 2002 - 00:41
Anoying, isn't it.
I had the same problem adding the MSDE2K to my install. The end result was that they can be ignored. If you compile your build into a single exe release, then the warnings don't occur.
If you want more information about the warnings, then you can search the InstallShield Developer 7 newsgroups. I have added the some responses which I received about the subject below:
****************************************
Hi,
in my opinion, that is not the error!
The error is generated at build time!
When you look after the build in your final MSI-Database, you will see in file-table two components with the same DLL.
These DLL's are part of the MSDE-MM.
I think at build-time, for every component with files a entry is made in this table and the file is copied to Disk1-Folder.
Now when the second component is inserted and his file is copied, a warning is generated.
This is a little bug in the Developer-Build-Process.
I hope, that Joshua from Installshield read this.
We have also discuss this error under the link
see
regards
klaus
****************************************
These warnings are harmless.
I see them in my project when I build an uncompressed release of the installer. When I build the same project, but a compressed release, I don't get the error.
(Why build an uncompressed release? With >150MB of files to collect, it's much faster to skip having to compress them all.)
Joshua's response in the other thread is irrelevant, as the MSMs in question are the 25 MSMs that make up MSDE 2000, and we really shouldn't have to /cannot determine where the files come from.
Drew Liscomb
***************************************
I hope this helps.
Regards,
Sijmen.