>>Outside of the set up wizard what other installers are people using out there.
>
>We have clients that run maybe 4 or 5 of our apps, so they only need to install the runtime once. So we distribute an InstallShield that loads teh run time. We also wrote an App Manager which can install and update our apps from a "Files" table we distribute in self extracting WinZip files.
>
>We basically wrote our own installer, why? Well, this way we can
>
>A. Be able to back up an app before we isntall it.
>B. Have full control over what happens if a special setup type is used (Just the Client, the Data, or Both).
>C. Be able to include Hooks that the App Manager can use in the Files Table.
>D. We call SDTs Update on our DBCs right in App Managers Update.
>E. We can hanlde errors better, like seeing if users are in the system
>F. We can have options like "Download the latest version of this app" in the Manager
>G. Be able to run the app when we're done
>H. Just about everything else our little heart desires :-)
>
>I know alot of these can be done with VI or ISExpress, but it almost seemed simpler this way. Its pretty flexible, but powerful too. And it only takes minutes to create an install routine for a new app.
>
>>4) Third Party data server
>
>You mean like MSDE or SQL Server?

No, it's a vehicle parts and labor guide for auto repairs. It's a DCOM app that needs to be included for our app to work properly.

__Stephen