>>My present employer runs a few VFP applications over a Novell WAN.. When they started upgrading to the newest Novell client (3.30) the applications they run started to hang at the start of the application running.
>>
>>We have found a partial solution, but it does not really make sense.. The Novell 3.30 client installs TCP/IP as the default protocol. The 3.1 client was using IPX as the standard protocol, when we switch the protocol back to IPX for the affected workstations, the problem disappears..
>>
>>Should VFP really care what protocol it uses to communicate with the network?
>>
>>And bigger question, why does this only happen with the runtime? Running applications off network through development version of VFP do NOT hang at all?
>>
>>All workstations are running Windows 95, run-time files and application files are on the network.. (Long story....)..
>>
>>Anyone have any ideas??
>>
>>Please advise....
>>
>>Thanks!
>
>Not quite clear on what you're saying. You have problems when both IPX and TCP/IP are installed. What are you doing to fix it?
>
>- Removing TCP/IP entirely, or
>- Leaving both protocols present, but setting IPX to be the default protocol in the Advanced tab of its Properties?
>
>If the former, you have a problem, because you probably need TCP/IP for other non-Fox stuff. If the latter, that's your fix, you don't really need to do anything else.

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??