The merge modules were updated on January, 23. Are these the same ones you are using?


>Yes, downloaded from Crystal Decisions support site. They confirm in a phone call that I have the right ones. My original problem, with InstallShield 3.5 sp4 was that the Installer would reactivate about 6 or 7 times right at startup of my VFP app, when the Crystal runtime had not been called at all. Crystal referred me to http://support.installshield.com/kb/view.asp?pcode=ALL&articleid=Q106852, which states at the very end that IE4 eliminates the problem. So I spent my good money to upgrade. I thought initially that it DID solve the problem, only to discover that the Win Installer still kicks in when "CrystalRuntime.Application" is instantiated.
>
>Now yet another mystery: That IE test install was on my wife's machine. She runs a VFP gradebook that I wrote for her several years ago. It's a compiled app in a completely different folder, different data, different everything--absolutely no connection to Crystal. It calls MSMAPI to send email grade reports to her students, and when it does so, bingo, up pops the windows installer attempting to re-install my new app! Bizarre!
>
>Oh, and just for the record, it's not just that computer; colleagues at my company have seen the same problem on at least three other independent installs, one on WinXP, one on Win98. BTW, on my development machine and on a notebook, both with full Crystal Developer 9.0 installed, there is no problem whatsoever; everything works as advertised.