Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
2nd database corruption in 2 weeks, who did it?
Message
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00182124
Message ID:
00182178
Views:
13
>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.

Thanks George.
Previous
Reply
Map
View

Click here to load this message in the networking platform