>>I tried going through the setup wizard. It appears the setup wizard makes a slew of changes to the NT registry and copies numerous support files to the local disk. Well this is not cool when all my users are restricted from doing this. (Having this restriction is why I chose NT in the first place!) When I did install it on a work station it ran fine from the local copy as administrator and as enduser - but I need it to run fine from the network. Is there a way I can just do the VFP6 runtime installation for the end users? And then be able to deal with exe's on the network like I used to in 2.6?
>
>My approach has been slightly different from Ed's, but requires more work from me. 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.
>
>My way is probably more work at each workstation than Ed's, but it's worked for me.
>
>Regards,
>Rich.

Thanks for the tip and I think I tried what you suggested the way you indicated but it still doesn't work! Get the same error -
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.
Set up from network directory completes without error.
When I click on Start/VFP APPS/Supervisor System I get the error.
When I run it from c:\supsys I get the error
When I run it from h:\super I get the error.

What am I doing wrong? (Oops! I didn't reboot - let me give that a shot and report back!)
S