>Really, to use the setup wizard is the best way to send your exe to your client, Using it you don´t worry about necessary files ...
I agree. However, there are cases where it is really simpler to know - and distribute - the 2 or 3 DLL files required (the file whose name includes ODBC is only required if you use ODBC). For instance, I placed an EXE in a shared folder on the network, and the VFP*.DLL files in the same folder. In the beginning, this saved me the trouble of running the setup program on each and every machine.
Later, however, it turned out that the users required access to EXEs in many different folders - and since I found it impractical to keep a copy of the DLLs (ca. 4 MB) in each and every of those folders, I finally created a "dummy" installation program that installed just the DLLs.
Oh, right, and it also included support for the help system and some ActiveX controls. So if you need all that, the Setup Wizard is the most convenient way to go.
Hilmar.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)
