Windows installer pops up briefly after launching app built in VB6
| Oh. That's odd. I don't understand your description,
| though. You said if you just "build a standard EXE"
| then it's fine. It sounded like you were saying that
| only the installed version is acting up. But that's an Inno
| install? Weird.
|
| You might still get help in the MSI group... or even the
| Inno forum. I've seen similar questions in the MSI group,
| with people who *are* using W.I. If I remember correctly,
| the cause then is typically a damaged/aborted install, causing
| Windows Installer to jump in every time the program is run.
|
| Sorry that I don't have a better answer. If it were me
| I think the first thing I'd look into is to try to figure out
| what, if any, installed program is connected with the
| W.I. invocation. Then try re-installing that.
Yeah, it doesn't matter if the OP is using WI or not. It has to do with
shared files, and sometimes other appilications installed by MSI that share
VB runtimes will trigger the MSI to repair it's installation if some of
those files are damaged or missing.
For example, Office install the mso.dll in common files. So does FrontPage,
even tho it's technically not part of Office. Since both are installed by
WI, if that file is damaged, deleted, whatever the launch of with
application will instruct the MSI to attempt to replace/replair the mso.dll
file. Typical MSFT logic.
AFAIK, the only thing the OP can do is track down and remove whatever other
program is sharing the files with VB. It's happened to me and a few of my
end users on occasion when someone who used WI to install their app didn't
set it up properly. I've used RegClean before, but it's not something I
would recommend to others unless they backup their regsistry.
