I don't feel I've given you much help here but you're welcome for whatever help it's been.

Good that you figured out the cause. It's hard to understand how including a system merge module or modules would have that effect, though. I'll take a look at those three MSMs and see if I can figure out what they're doing. Meanwhile if you want to send me your MSI file you can still go ahead and do that.

One other question: does it seem to make a difference what version of Windows the target machine is running?


>Thanks a lot Rick.
>While reading your answer, I suspected what was happening.
>My setup includes some ActiveX and some Merge Modules.
>The VFP9 Merge Modules, the MSXML4.0 Merge Modules and the MSXML3.0 Merge Modules, for example.
>
>This last one (MSXML 3.0) is the origin of this problem.
>Whenever I include the 3 merge modules:
>
>MSXML 3.0 (msxml3_wim32.msm)
>Msxml3 Exception INF Merge Module (msxml3inf_wim32.msm)
>WebData std library (wdstddll_wim32.msm)
>
>All the files in the INSTALLDIR are deleted during the setup.
>
>Furthermore, if I install and immediately uninstall, two files remain in the INSTALLDIR: msxml3 and msxml3r
>
>If I remove these merge modules from the setup project, everything runs as expected.
>
>So I suspect of a bug in these merge modules.
>But in VFP9's Installshield walkthrough they say you have to include these merge modules if your application uses cursortoxml() - which I do a lot.
>
>So, this explains me the cause, but I don't have a solution.
>What do you think Rick ?
>
>P.S.: Thanks a lot again for the enlightment the led me to the finding.
>
>
>
>
>>I can't reproduce this behavior with a test install (although I should point out I am using InstallShield Express 5.0 SP2 full version, not the Limited Edition of version 5.0 that comes with VFP 9.0). If you want to, do a CD-ROM type of build and then e-mail me the .MSI file it creates (not the SETUP.EXE, just the MSI file, which should be fairly small since it does not contain any of your application's file). By looking at the MSI file we may get a clue as to why this is happening.
>>