[Samba] Strange Problem with Access

[Ruben Fagundo]

For the database experiencing problems, there was not ldb file found.  I 
did  find an ldb file for a completely different database, but not for the 
one that is causing me all this grief.

I have added the /*.ldb/ to the veto oplock option to see what happens.  I 
also downloaded 3.2.3a sources, and I'll be installing it over the 
weekend.  I'll keep everyone informed of what I find.

Thanks for the input,
Ruben

At 02:00 PM 3/8/02 -0600, Glenn Scherb wrote:
>Access opens *.ldb file that does the user-level locking.  These can get
>corrupted when an application exits ungracefully.  A symptom of a
>corrupted *.ldb file is that Access reports the database is opened
>exclusively by another user.  Check to see that no one is actually using
>the database with smbstatus and delete the *.ldb file.  The database
>should open normally.
>
>--
>Glenn Scherb
>Midwest Research Institute
>425 Volker Boulevard
>Kansas City, Missouri 64110
>gscherb at mriresearch.org
>http://www.mriresearch.org
>
>Phone: (816)753-7600 x1806
>FAX: (816)753-5359
>Page: (816)990-8513
>pagegscherb at mriresearch.org
>
>
>
>-----Original Message-----
>From: samba-admin at lists.samba.org [mailto:samba-admin at lists.samba.org]
>On Behalf Of Bill Moran
>Sent: Wednesday, March 06, 2002 7:45 PM
>To: Ruben Fagundo
>Cc: sbawa at tabmaster.com; samba at lists.samba.org
>Subject: Re: [Samba] Strange Problem with Access
>
>
>Ruben Fagundo wrote:
>
> >
> >>
> >> I set the following options up and I still seem to have the same
> >> problem.  Did I set the oplock setting correctly???
> >
>
>It looks right, as best as I can tell.
>
> >> I get the following error message, exactly from the win95 machines:
> >>
> >> "The Microsoft database engine stopped the process because you or
> >> another user is attempting to change the same data at the same time."
>
> >
>
>Could it (possibly) be some other problem with the Access file itself?
>(just speculating)
>
> >>
> >>
> >> The pertinent setting in smb.conf are as follows:
> >> ===================================
> >> [global]
> >>
> >> veto oplock files = /*.mdb/*.MDB/
> >>
> >>  [public]
> >>    locking = yes
> >>    oplocks = yes
> >>    veto oplock files = /*.dba/*.dbm/*.mdb/*.MDB/
> >>    share modes = yes
> >>    strict locking = no
> >>    comment = Temporary file space
> >>    path = /home/apps/public
> >>    public = yes
> >>    writeable = yes
> >>    create mode = 0777
> >>    directory mode = 0775
> >
>
>Doesn't Access use some other sort of file? .mde or something?
>If you run "smbstatus" while Access is running, what kind of locks
>does it show on the files?  Check that out to see if it's working, and
>if
>you've got all the apropriate file patterns.
>I would suggest two things (in order):
>1. Try turning off oplocks altogether
>2. Figure that I was wrong about the oplocks and look at other
>possibilities.
>
>How much would it take to install MySQL and put the Access database
>there?
>MySQL works great with Access through the MyODBC driver. (I know this is
>changing lanes without signalling, but I just thought I'd throw it out
>there.)
>
>-Bill
>
>
>--
>To unsubscribe from this list go to the following URL and read the
>instructions:  http://lists.samba.org/mailman/listinfo/samba