>>>I can't help with your problem, but having recently switched to Client 32, the only thing I can say is that it really "barks" and that it should be AKC certified. I hate it, but if that's what the client wants...well. he'll have to live with it. Bottom line, VFP's the victim and Netware's the culprit.
>>
>>George,
>>
>>scuse me for asking , but what does AKC stand for? ... and are you saying thqat we should revert to Microsoft Netware Client ?
>>
>>Marc
>
>Sorry, Marc, I forgot and was playing "The Ugly American".:-) AKC stands for American Kennel Club. The certify breeds, etc. of dogs.
>
>If I had my choice, I'd go back to Novell 3.1x. Since we've switched, we've had such fun. That is if you consider numerous crashes on your workstation "fun". Netscape has GPFed at least 5 times today. That never happened before.

So it's not only me switched back in a hurry to Netware 3.1x. Fortunately I was intelligent enough to set the new one on another server at weekend and when I saw the crashes (and definitely incorrect max number of connections exceeded messages) by monday switched all back to original server and never could make Novell 4.x and up work as good as 3.1x. Placed it on the shelf as a licensed and never used product enriching the decoration.
Novell IPX/SPX is somewhat better than MS's but MS Netware Client let you work smoothly with win apps (if you want to play Doom, Duke etc then prefer Novell IPX). No problem, no headache. Compared to NETBEUI, Netware buffering just sucks and makes the system come to its knees with large volume transfers. I upgraded one of my sites to NT and trying to get rid of Novell on the other site too (Novell is quite expensive to do disk sharing in a world where NT exists).
Cetin