A client of ours has a VFP 6.0 SP5 DB on a Novell 5.1 server and is using the following Novell client settings:

- file caching = ON
- large internet packets = ON
- packet burst = ON
- true commit = OFF

They've experienced some DB corruptions and locks being held (even after reboots) since opening the app to multiple users. Based on our experience and investigation via Google, Novell support, and MSDN, we believe that they really need to switch the Novell client settings above in order to ensure the integrity of their DB.

Unfortunately, their IT folks aren't prepared to make those changes, because they aren't "standard". But, they do have a Windows 2000 PC (not a server) on which they could place the database and then have the various DB users access it using a mapped drive (basically a peer setup using the MS file and print sharing drivers).

But, my understanding is that some Novell client settings will continue to impact file access even on non-Novell servers. Is that true? Or, can we expect the peer access to the shared drive on the Windows box to adequately provide for no caching, etc.?

Thanks in advance for any info you can provide.

ewb