>>>Hi All.
>>>
>>>I have a VFP 3.0b app that has been in production for about a year and a half. It ran fine under Novell 3.11. Recently we upgraded to Novell 4.1 using Novell's client32 version 2.5. Immediately, this app had almost daily memo file corruption trouble. We turned of packet burst and caching, and it seemed to resolve the data corruption problems with other db's like paradox. But I am still having the problem with the VFP app. And when running from the command window, I constantly get problems with VFP not responding. Can someone sell me a clue?
>>>
>>>TIA
>>>
>>>Marcia
>>
>>Marcia,
>>
>>Did you have your net people take a look? Sounds like a network problem.
>>
>>Paul Harker
>>ECNE, NetAnalyst
>Hi Paul.
>
>They have been trying to fix this problem for a couple of weeks without success. I was hoping to get some information that would help them.
>
>Marcia

Have them e-mail me so we can get specific. Have they put an analyzer on the line? Do they have one? I suspect network problems if VFP is unresponsive or very slow. The only way to tell what is happening on the network is to put an analyzer on the line, and capture packets from your station to the server. You can see that data that was sent from your station, what went over the network, and you server received. If there is a difference between the two, you have to start eliminating possibilities (re-install client, test with different cables, different port on hub, etc.) Also test from different stations (different cables, network card, hub port). This will also tell if the client software is the culprit as Wayne states.