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

Marcia:

This has been a problem for quite some time. Novell supposedly fixed the problem with the 2.5 release of their client, but I haven't seen anywhere that it runs correctly.

The way we get by it is to go back to the MS client and use Microsoft's Client for NDS.

HTH
Wayne