FW: Record locking

[John Esak]

I'll post this for you... it is interesting...
John Esak


-----Original Message-----
From: ken white [mailto:kenwhite at arcticinfotech.com]
Sent: Wednesday, March 31, 2004 2:57 PM
To: John Esak
Subject: Re: Record locking


John I cannot seem to post to the filepro news group so I sent my response
to you.

----- Original Message -----
From: "John Esak" <john at valar.com>
To: "filePro mailing list" <filepro-list at seaslug.org>
Sent: Wednesday, March 31, 2004 12:34 PM
Subject: RE: Record locking


> >
> > As drives and computers get faster, timing problems are bound to happen
> > especially with windows based systems.
> >
>> So when people talk about even more strange things like write caching of
one
> kind or another and faster networks and etc.... it all makes no difference
> if the record is locked properly and filePro certain does _its_ part of
the
> job in this regard.  Otherwise, we all need to see such misbehaving code.
> As you say, your problem is most likely outside of filePro.
>

I do know if this is an the issue with filepro under windows,

XP / NT / 2000  - OpLocks

I have run into database corruption on other databases if OpLocks is turned
on ( enabled ) when using the above OS's.

The following registry key controls Oplocks.

Server Side (2000/XP)

HKLM/system/currentcontrolset/services/lanmanserver/Parameters/EnableOplocks

Client Side:

HKLM/system/currentcontrolset/services/MRXSmb/parameters/OpLocksDisabled