Creating a setup routine with the setup wizard will do this all for you (once you run it on the workstation).

>Putting the Dlls in the program directory is how that place I'm at now was doing it. But I changed that, because as I understand it, the DLLs need to be registered in VFP6.
>
>PF
>
>
>>>I am loading my executable file on a network, where does the vfp500.dll file need to go? Do I have to install this on each individual workstation, or can I put it somewhere on the network?
>>
>>It is intended to be on the c drive in your windows system directory.
>>
>>>Do I need to install this from the VFP6 cd-rom every time I install it, or is there an easier way to do this without having to install all the other items from VFP6, like Microsoft IE and such.
>>
>>What I find easiest is to create a dummy install that just installs a TXT file onto the client machine. I bundle this up with the VFP setup wizard. This takes care of putting all the various DLLs in the right place. I then put this onto the network then I or the users can do a VFP runtime install.
>>
>>An alternative (but unsupported method) is to put all the runtime DLLs into the same directory as the EXE either on the local machine on on the network.