>First of all, thanks to everyone for the quick responses and support.
>
>The index corruption hasn't a standard pattern. It isn't on a particular table, field, expression, length, tag, etc. I can't find any pattern. I know it strikes when we load or unload the network heavily. I get corruption around one of three points in time every other day; in the morning, just before lunch, and just before the end of the day.
>
>We have an NDS tree here on the Novell 4.1 Server.
>
>Which Client32 version were you using when there was corruption?
>Has there been a fix in a more recent version; as stated earlier our current plan of action is to use the Novell login script to update all workstations to the latest version of Client32 version 3.1 with some specific cache settings.
>
>Can the MS Client access all the same features as Client32 ?
>That is to question, will the network admin have an aversion to switching clients due to a loss in features or functionality?
>
>Is there a means to do a mass conversion of clients to the MS version, rather than touch each of the workstations? (Novell has the means of course)
>
>Thank you all again,
>Steven Marin

It has been my experience that most network admins will get very nasty if you tell they must switch. When that was the case, we gave them the NT Workstation solution, and several have gone that route. The MS client has the majority of the features available in Client32, but I am sure there are some things missing.

Put it this way, if there is some kind of business office manager, ask him if he wants to spend hours every day with no system and have a nice administration tool for the network administrator... or have a stable system that is up all the time.


Wayne