[Samba] MS Access and AccPac

[Eric Anderson]

It has been my experience that setting:

oplocks = no
level2 oplocks = no

on a per share basis is required for more than 2 users connected at the 
same time to a particular file to avoid problems. The oplock contention 
level is 2 by default, so more than 2 users requesting an oplock for a 
file starts to cause confusion.

If you are using a database application such as Access, it is NEVER 
advisable to use oplocks in the first place. The only reason for oplocks 
is to boost performance over the network by caching files locally to 
work on them. This should never be attempted for a real-time database.

This is not to say that regular file locks are not in place with the 
above options, just the caching locks.

Hope this helps.

-- 

Eric Anderson
Systems / Security Administrator
21st Century Electronics



Rodger Haynes wrote:

> I am looking at migrating our Access2000 database and AccPac 
> accounting functions onto a Linux 7.1 server with Samba 2.0.7. I have 
> installed the Pervasive2000i server evaluation and all appears to work 
> OK. I've only used 2 clients and didn't appear to get any locking (or 
> not locked) problems. Both AccPac and Access run with data on the 
> server and application files loaded locally. The network has only 20 
> or 25 Win 95/98 clients, and security=user. Can anyone point me toward 
> information on problems to watch out for and settings to use. My main 
> concern is file integrity and avoiding corruption. The number of 
> postings regarding oplock problems has me concerned. Thanks in advance.
>
>
>