>Okay, I will try and explain a little better this time.. We are loading a newer client for Novell (3.30) over the current 3.1 client. The protocol we used for the 3.1 client was IPX. The protocol we are trying to use for the new client (3.3) is IP (or tcp/ip) when using this setting, VFP applications running over the network are locking up upon loading. The runtime files are located on the server, along with the application files..
>
>When the new client (3.3) has the protocol set back to IPX, we have no lockup problems, but the network support staff do not want to support the network using this protocol....
>
>So, what would this suggest??

A few things to think about...

Is the TCP/IP stack supplied by Novell, or Microsoft? If Novell, can it be removed and replaced by the MS stack?

Are there any tricky IP router configurations or proxy servers on the network? Are the workstations running IP proxy clients, and if so, are those set to bypass the proxy for intranet addresses?

Are you running any antivirus software either on the server or workstations? Can you test with them disabled?

You mention in another part of the thread that the problem manifests itself with runtime VFP, not the dev environment. Is it possible that the dev environment has different server permissions than the runtime users? You should check permissions for temporary file folders as well (both network and on the workstations if NT/2K).

In general it's not good practice to have the runtime files on the server (various VFP registry entries are not created/set). A runtime-only installation should be done on each workstation. One way to do this is to create an installation directory containing just a single text file, say DUMMY.TXT, firing up the VFP Setup Wizard and creating a NetSetup of just that file, including the VFP runtime. It might be enlightening to try that on a machine with the problems.