>I sympathize, believe me, I've had my own set of problems with Client 32. These include table corruption, index corruption, Win386 read errors with FPW. My experience with the corruption leads me to believe, that the larger the size of the table/index, the more likely this is to occur. These problems don't occur with MS's Client. Novell seems to think it has to do with the number of file handles FoxPro uses (which can be quite large). Further, they state that Netware 5.x fixes the problem. As we say in the states, Evan, "I'm from Missouri" (meaning I'm skeptical) on this. I'll believe it when I see it.
>
>For me (and my users), not to mention the network guys, this is a major league PITA. From the moment I laid eyes on Client 32, I didn't like it. For my money, it's too difficult to control, and simply too agressive.

Agressive is the right word. I've had to install it once temporarily (made a small Novell network with two stations for just one show), and it took months to kill later. Eventually I had to reinstall it and then uninstall, and then it died gracefully. In the meantime, anytime I added/removed any component which mentioned a 'n' of a network-related issue, it demanded its CD (what CD, I installed using DOS client to get to install from the server), complained of missing .vxd's while booting, and bored me to death.