>What is stopping you from copying the installation files to a network volume, and having folks run the setup from those files? Or, is it a big issue to have this done automatically?
If you try to install TO the network, the setup program terminates and tells you to use the /F switch option. When you do that, the installed files retain their compressed names (.ex$, .dl$, etc) So you have to install to the local drive, then copy the files to the network. (that's the official MS workaround) Since i wouldn't trust the end-user with the install, I'm doing it myself. It's more work to run the setup and copy the files than to copy the installation from the developer environment.

>You can copy the DLL's manually, and your EXE will run..
I think this is what i wanted to know - to say goodbye to the crippled wizard

>As for lazy development...hey, you do what you gotta do...
Well, what is lazy today may be a lot more work when modifications are necessary. "Good" code is usually easy to code AND maintain.

>Geez, I just realized you are a stone's throw from me.... Good luck..
Um, are we going to start throwing stones now? hehe...