>>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!
>
>There are known issues with Novell clients... they just do not play well with VFP. The only solution I have ever been able to come up with is to switch to NT and use the client that runs on it. Otherwise, you are spinning your wheels. I would also question whether it is only the runtime... are you sure you are placing as much load on the system when testing in development as when your users are when they are actually running the program?

Wayne,
I am very confident that the load is the same, since when we do simple testing of the application, it freezes up on our machines.. Remember, the freeze ups occur whenthe application first loads.. Why would VFP care if we are using TCP/IP or IPX network protocols?

Are the MS VFP techies listening to this thread?? Mike Stewart, Any ideas??