>>I've made setups which place a PM item for the app. The created PM item points to the app the setup places on the local hard drive. I run the install on each workstation (logged in as administrator) which will use the app, to get the necessary registry changes and runtime files installed. Then I delete the directory with the app which I just installed on the local hard drive, and change the PM item to point to the network app.
>
>I ran through the setup using h:\apps as the source for the code. Included in the directory were the executable - super.exe and a handful of icons and bitmaps. The Dll's vfp6r and vfp6enu were also in this directory. (This is the network directory the users will be running the super.exe from.)
>I had it create the network installation to h:\setup. I had it create a directory on c:\supsys for the local app install and create a PM item for it.

Putting vfp6r.dll and vfp6enu in the app with the exe is not necessary. What is necessary is to check the box in the setup wizard which says to include VFP Runtime Libraries. There are several more dlls than the ones you mentioned which must be included, and the Setup wizard brings them in from the directory on your development machine where you installed VFP, not from the directory in which you tell it to find your exe.

HTH,
Rich.