>>>It could be that you VFP runtime files are not copied and registered to the system directory on a non-development box.
>>>I'm curious as to why you would use Install Shield to launch the FoxPro setup program. You don't need to use the setup wizard
>>
>>
>>I routinely use a Setup Wizard distribution containing the VFP runtime within InstallShield scripts to put the runtime in place - create a WebSetup, throw it on the distribution CD, and fire it silently using LaunchAppAndWait() in my script with the appropriate command line switches - that way I don't have to keep track of the VFP runtime requirements within the script context. YMMV, but it's really easy to do, and the one thing Setup Wizard does do well is put the runtime in place.
>>
>
>Sorry Ed, I didn't see your reply earlier. What you describe is exactly what I'm trying to do too, except that I'm using the NetSetup instead of WebSetup. The reason I'm doing that is that info on the Wiki seemed to say that you couldn't run Websetup in Quiet mode, whereas you could on the Netsetup routine. From my testing this afternoon, this also seems to be where the problem crops up - the Netsetup routine produces a Setup.exe - InstallShield Express also produces Setup.exe (invoked by Setupex.exe if you build the single file). It looks like IS's Setup.exe won't load another prog named Setup.exe into memory while the first is running. What I had to do is rename the Setup.exe from the VFP wizard to something else (wksetup.exe), which also forced me to rename setup.lst to wksetup.lst, and I had to change entries in setup.lst to match. After doing all this, I got it to work. Strangely enough, we used to a similar setup routine with PCInstall with no problems at all.
>

I use InstallShield Pro (just upgraded from 5.2 to the 2000 product) so I've got considerably better control in scripting than you might with Express
>Rod Poujade
>Montreal, Canada