Record Locking Not Working

[Kenneth Brody]

On 4/23/2014 7:54 PM, Del wrote:
> Ok, I created "Testfile" (very original name) with 2 fields, first and last
> name, 20 characters each.
> Added 10 records to the file, all blank.
> Got into update mode on record 1.
> In another session, brought up same file, went to record 1, and was able to
> get into update while session 1 was still in update mode.
> Same overall behavior as before.
> That's it in a nutshell.
[...]

Grab a copy of SysInternals' "Process Monitor":

     http://technet.microsoft.com/en-us/sysinternals/bb896645

Run it with "procmon /noconnect", which will stop it from monitoring upon 
startup, and will wait for you to manually start it.  (On my box, it was 
logging over 10K events/second, so you want to keep it to a minimum.)

Start two dclerk sessions, showing the same record, not in update mode yet.

In ProcMon, press Ctrl-L to bring up the filter.  Press "reset" to make sure 
the filters are set to the default.  Then add the condition:

     Path
     Ends with
     Testfile\key
     Include

Click "Add" and then "OK".

Then, as quickly as you can (no need to panic, we just want to minimize the 
logging):

     Press Ctrl-E to start logging.
     Switch to the first dclerk, and press "U".
     Switch to the second dclerk, and press "U".
     Switch back to ProcMon and press Ctrl-E to end logging.

The logs are supposed to show that the first dclerk succcessfully locked the 
record and then read it, followed by the second dclerk failing to lock the 
record.  (See attached screenshot.)

What do you see for the locks?


FYI - Don't worry about any "buffer overflow" items.  That's apparently 
normal behavior, and really means "there was more data available than would 
fit in the buffer you gave, but since the API call includes passing the 
buffer size, nothing bad happened":

 
http://blogs.technet.com/b/markrussinovich/archive/2005/05/17/buffer-overflows.aspx

-- 
Kenneth Brody
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Capture2.PNG
Type: image/png
Size: 62664 bytes
Desc: not available
Url : http://mailman.celestial.com/pipermail/filepro-list/attachments/20140423/b697eec8/attachment.png