Doug,

>>I have finally converted my apps from VFP6 to VFP9. After much sweat I was trying to use InstallShield Express Limited (5.0) to create the setup file. I keep getting the 2908 error, possibly indicating an issue registering a dll. I hit OK and the setup seems to install correctly and the app seems to run. This would be livable for me BUT I have to give the clients a copy of the setup file and it doesn't look too professional. Also I don't know if there may be any side effects of this error. Has anyone seen this error and have any suggestions how to fix it or why it is happening?
>
>I strongly recommend abandoning InstallShield Express (ISX). First, the version that comes with VFP is very old by now. Second, it's very slow, both to generate setups and for the user to run. Third, as you've found, errors are very difficult to track down and fix.

>I, and mInnony other VFP developers, use Inno Setup. It's free, fast, easy to learn and to use, and eliminates all of the problems ISX has. I have a white paper discussing how to use it to deploy VFP application at http://doughennig.com/papers/default.html.

We use both. For our client install for our applications we use ISX. One advantage of that is that you can use merge modules. Just click what you need and you are done. WIth inno setup you'll have to deal with all individual files in the merge module which is much more complex to get it right. We've included the runtimes of Leadtools and Crystal reports which are close to a hundred or more files that need to be put somewhere. For a mortal developer its a challenge to put the files where they belong.

OTOH, we use innosetup for all the updates of our products because it containes a small number of files is much more customizable and can be generated from within a VFP program.

Next year we have to update our client install because of additional activeX controls and other libraries. I think we still do this in ISX because it probably is easier to do rather than converting everything to Innosetup.

As far as slowness of ISX. I've not found that ever to be a problem.

Walter,