Opportunistic locking should be turned off on the client and on the server as a rule of thumb. That way it will never be an issue. Also, it is very important that they use the latest version of the Novell client for Win98 because many bugs were fixed over the years. Additionally, ensure the cache setting is correct. Do you have a mechanism in your app that tracks when users exit your app incorrectly? Can you tell if a user turned their workstation OFF or if they killed your app by ending the task? Does the site have reliable connectivity between the workstations and the server? Are any packets being dropped? Poor wiring maybe or bad ports on the hub/router/switch? What are the settings on all of the workstation network interface cards? If you force the NIC on the workstations down to 10mbps/full duplex (as a test), do the problems go away?


>So, if CLIENT FILE CACHING ENABLE is set to OFF on the Novell server and all of the customer's client workstations are using the Novell client then OpLocking is automaticaly turned off? Is this true with Win98 clients as well?
>
>Does closing DBFs after updating help reduce data corruption on Novell?
>
>I've got probably 40 Novell sites and only a few are giving me fits with data corruption.
>
>Thanks,
>Ken
>
>
>
>>For a Novell network, set it on the server if the client uses Novell client software. Setting it on the client is optional but recommended always. If the client is a mixture of Novell and/or MSFT clients then set it on the workstation always also. It is best to use the Novell client fo this very reason. The Novell client is oplock aware, meaning that if file caching is enabled on the workstation then the cache manager is invoked automatically and vice versa. Also keep in mind that OpLocking uses broadcasts and then waits for ACKS.
>>
>>>So I have to have BOTH client opportunistic locking/caching and server file caching turned off?
>>>
>>>Here's what I currently have them setting:
>>> Win 98 machines - CACHE WRITES = OFF
>>> FILE CACHE LEVEL = 0
>>> TRUE COMMIT = ON
>>> OPPORTUNISTIC LOCKING = OFF
>>>
>>> Win 2000/XP - FILE CACHING = OFF
>>> FILE COMMIT = ON
>>>
>>>So I have to tell them to set the server CLIENT FILE CACHING ENABLE to OFF also?
>>>
>>>Thanks,
>>>Ken
>>>
>>>>Hi,
>>>>Also Client file caching enable has to be set to OFF on the server, you can check the setting in Monitor/Server Parameters/NCP.
>>>>
>>>>>Has anyone used the new FLUSH FORCE in VFP9 with DBFs residing on a Novell Server? If so, has it helped with the occurrences of corrupted data? All of my Novell customers have been instructed to turn off opportunistic locking,etc. on their client machines but I still have several that get corrupted DBFs on a regular basis.
>>>>>
>>>>>Thanks,
>>>>>Ken