Bob, Another thing to check--I think I remember that the Samba people changed some of the default locking options. I recall a lot of discussion about this on comp.protocols.smb and some on comp.databases.ms-access
Included below is an old message I saved (which may or may not apply to your samba version) I strongly agree with the writer that says that Access should only be used as a front-end tool, if at all. Ralph >From: David Collier-Brown <[EMAIL PROTECTED]> >Newsgroups: comp.protocols.smb >Subject: Re: File locking with Access db >Date: Fri, 28 Jul 2000 13:18:32 -0400 >Xref: news.efn.org comp.protocols.smb:47957 > >Greg McLaughlin wrote: >> We're trying this also. Initially I had the same problem with only one >> user being able to be in the Access mdb at a time. These settings for >> the share where the Access mdb's are in make it work, but obviously it's >> not very safe and secure so that needs to be figured out still, but this >> was my first successful way to let multiple people use the same mdb, so >> there must be something about the permissions samba places on the .ldb >> Access creates after the first person starts the Access mdb. > > Nearly-on-topic rant: try always to use access > as and "access method" to a back-end database. > > While you can get access to share the underlying file, > (see below), this doesn't scale up. MS says to use > a back-office database, and I quite agree. I just tend > to reccomend a different database vendor (;-)) > >--dave > >Ps: HINTS.txt says: >Here are some notes on running MS-Access on a Samba drive from Stefan >Kjellberg <[EMAIL PROTECTED]> > >1. Opening a database in 'exclusive' mode does NOT work. Samba ignores > r/w/share modes on file open. > >2. Make sure that you open the database as 'shared' and to 'lock >modified > records' > >3. Of course locking must be enabled for the particular share >(smb.conf) > >And I say > >4. Put the databases in their own share > >5. Turn off oplocks on the share. > > >-- >David Collier-Brown, | Always do right. This will gratify some people >185 Ellerslie Ave., | and astonish the rest. -- Mark Twain >Willowdale, Ontario | //www.oreilly.com/catalog/samba/author.html >Work: (905) 415-2849 Home: (416) 223-8968 Email: [EMAIL PROTECTED] --- At 09:57 PM 11/28/2001 Bob Crandell <[EMAIL PROTECTED]> wrote: >I copied the database to a WinDoze computer as a work around until I can >find a real answer. I sure hope this isn't what they end up with. I'm >trying real hard to "sell" them phpGroupware. It would be the pits if I >have to put in an NT box. > >Thanks > >On 2001.11.28 14:02 kg7fu wrote: >> Check permissions in /etc/smb.conf (RH, MDK=/etc/smaba/smb.conf) >> under the shared directory entry. If it's on the remote win box, check >> that the database isn't using file locking. If it is, you'll have to >> either >> use a copy of the .mdb or move it to a neutral box and let the clients >> share. >> >> - jk >> >> On Wednesday 28 November 2001 10:21, you wrote: >> > Hi, >> > I'm sorry to interrupt, but I have a client that is using Samba 2.2.?. >> I >> > just upgraded them to this. They are using an Access database that is >> > approaching 2 M. This all worked before the upgrade, now there are >> parts of >> > the database they can't get into. The worst part is somtimes it worked >> > yesterday, sometimes it didn't. Today it don't work. >> > >> > To repeat, they can get into parts of this database. There are parts >> they >> > can't access. The user is getting a message saying that someone else >> is >> > accessing that part of the database. This user is the only one logged >> into >> > the network. >> > >> > Does anyone know what the issues are with an MDB file and Samba and >> what to >> > do about them? >> > >> > I'm sending this before I hit Google and Samba's web site. >> > >> > Thanks >> >> _________________________________________________________ >> Do You Yahoo!? >> Get your free @yahoo.com address at http://mail.yahoo.com >> >> >
