[Samba] SAMBA and Microsoft Access

[Jon Robertson]

I'm trying to use Access 2002 on a Samba server.....question, are there
special Samba parameters that need to be set so that 3-5 users can enter
data? All users have proper access (no pun intended) to the SAMBA
server.....

thanks
jr

--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba

[Jim Wharton]

turn off oplocks for any share that holds the MDB files.

Jim

[richard]

Jim is this a "just in case" setting? Reason I ask we've used samba for
several years with no probs on "basic" settings! (2 small offices 6-8
pcs each, msaccess, off2k). Every time I read about oplocks I cross my
fingers....but nothing (with samba) has gone wrong so far!!
Richard Coates.

[Jim Wharton]

In the case of Access2000 and 2002, you will probably see problems with more
than one user accessing a database. I turn off all file locking on all
shares containing Access databases. Everytime you open an mdb file, take a
look at the temprorary ldb file that pops up in the same directory. This is
trying to lock out all other users. I have chased this issue round and round
and this is the only solution I can come up with.

On another note you may want to dump your tables into postgresql and use
linked tables in your access database/application. This is one way around
the problem. Access was never meant to be a shared database management
system.

[Freeman, Peter (ERHS)]

>In the case of Access2000 and 2002, you will probably see
>problems with more
>than one user accessing a database. I turn off all file locking on all
>shares containing Access databases. Everytime you open an mdb
>file, take a
>look at the temprorary ldb file that pops up in the same
>directory. This is
>trying to lock out all other users. I have chased this issue
>round and round
>and this is the only solution I can come up with.

The way we got around it here was to use the force user parameter, that
way the .ldb file is created by the same user that is accessing the db,
otherwise you'll run into hassles.

(and switch off oplocks on the share as mentioned above)

[Jim Wharton]

That is an interesting possiblilty...

Jim
----- Original Message -----

[Jon Robertson]

These are my settings....thanks for all of your replies...

security mask=0777
directory mask = 0755
directory security mask = 0777

These settings to the best of my knowledge were the defaults:
kernel oplocks = yes
locking = yes
oplocks = yes
level2 oplocks = yes
oplock break wait time = 0
oplock contention limit = 2
posix locking = yes
strict locking = no
share modes = yes

Thanks
JR

"Jim Wharton" <cre...@bellsouth.net> wrote in message
news:005e01c3009d$65b852f0$6401a8c0@solomon...

[Scherb, Glenn]

Set
oplocks = no
level2 oplocks = no
kernel oplocks = no

Access 2.0 is the only member of that family I've managed to get working with oplocks on.

Hope this helps.

Glenn

--
Glenn Scherb
Midwest Research Institute
425 Volker Boulevard
Kansas City, Missouri 64110
gsc...@mriresearch.org
http://www.mriresearch.org

Phone: (816)753-7600 x1806
FAX: (816)753-5359
Page: (816)990-8513
pageg...@mriresearch.org

[Noel Kelly]

There is also nothing to be gained running Access shares with oplocks - but
everything to lose. oplocks increase performance for shares handling mainly
static data by allowing the client to cache that data locally - Access is
flaky enough without introducing that sort of behaviour!

Noel

Hope this helps.

Glenn

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.471 / Virus Database: 269 - Release Date: 10/04/2003

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.471 / Virus Database: 269 - Release Date: 10/04/2003