>I have a client who wants me to create an executable that creates/updates registry entries. In doing so, I have created an install program using the setup wizard. That way, all the required dll's are placed on the users machine.
>
>Unfortunately, the client wants limited file placement to be done on the users machines. And wants the executable run from the network machine. Further, the client wants to keep those dll's that do not belong in the Windows system directory in the app directory where the executable is.
>
>Is there a good way to get this done?
>
>Any ideas are greatly appreciated...
>
>Michael

There is no reason that a DLL HAS to be in the system directory. As longs as, if it is COM it is registered, or if it is C-API it is in the current directory or DOS path. I think this even includes network drives. Give it a try.

BOb