>Trying to create an executable on a Netware volume which users can run directly from the network. I DO NOT want them to run a local copy of the application or any application components (reports). I understood from the documentation that VFP6 requires two files: VFPenu.dll and vfp6r.dll both these exist in the directory (H:\apps).
>Get an error: "Visual FoxPro could not start. Could not load resources."
>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?
>
It's trivial to create a runtime install only - create a single file in a distribution directory, and run Setup Wizard to create an install from the Web; include the runtime files, and do not mark any files as PM items. You're on your own at that point as far as creating shortcuts and the like - a post-setup executable could od it; the necessary functionality could come from several places; george tasker created a wrapper .DLL that's callable directly from a VFP app. This can be downloaded from the Files Section here on UT. My preference is to use installShield as a wrapper over the Setup Wizard, or use the Wscript.Shell Automation object of the Windows Scripting Host to handle the shortcut manipulation tasks from within a VFP application or Wscript using VBScript.
You'll want to install the runtime components and any common controls, in-process servers or out-of-process local servers, as well as the marshalling stubs for any remote out-of-process servers on each station. As you mention, there are a number of registry entires involved.
You're wrong about the required files for a VFP app, BTW; the file VFP6R.DEP in teh DISTRIB.SRC directory details the runtime system dependencies for VFP6. There are more than two files involved.
>Details: VFP6 - recent upgrade from FP 2.6, Novell Netware 4.11 patched to 5 (I use ZEN and application launcher to deliver desktops to the users. Almost all work stations are NT. Have a total of 10 VFP applications to manage and it's not unusual for the code to change daily in any number of them. that's why the distribution to local machines is not something I can live with. )
