>>As I just described to Hank, the application EXE and the set EXE are two different programs. So, if any ActiveX components got wiped out or whatever, the main application EXE would show an error. The main EXE knows nothing about the SETUP.EXE
>
>Are you sure? If the setup was generated in anyting using m$'s tools (forgot the name, just that it uses .msi extension), then it wrote in the registry which setup installed the app, so yup, the app itself wouldn't know, but Windowses would. Happened exactly the same way each time we had that. And mind you, our setup was generated in Inno, except the runtimes setup, which was a .msi - and then it went that way.
What you write may make sense. The SETUP.EXE used to be created using InstallShield, a MS product. Some years later I changed the SETUP.EXE to use InnoSetup. But it could be that the "old" setup is still in the Registry of the PC. What puzzles me is that it seem to have happened with - at least - two different desktops.
But I will check the users' drives for a MSI programs and delete them, if they exist.
Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
