fp file locking behavior

[GCC Consulting]

> -----Original Message-----
> From: 
> filepro-list-bounces+gccconsulting=comcast.net at lists.celestial
> .com 
> [mailto:filepro-list-bounces+gccconsulting=comcast.net at lists.c
elestial.com] On Behalf Of Bob Haussmann
> Sent: Monday, May 21, 2007 10:35 PM
> To: 'filePro Mailing List'
> Subject: fp file locking behavior
> 
> Admittedly, this post is a bit of a fishing expedition, but 
> we've exhausted our in-house testing abilities.  Platform is 
> Native Windows (ODBC) 5.6.01-5.6.06.
> 
> Occasionally (and unfortunately not in any way that we can 
> consistently replicate), we receive file locking errors in 
> fpsql or rclerk on various index files.  These files are in 
> active use, but only in add/update mode (*clerk, not 
> *report).  These don't appear to be record locks, but actual 
> file locks.
> 
> The only clue we have at this point is that *clerk appears to 
> open the key and active index file for writing, even when 
> simply browsing.
> I would appreciate it if anyone else can confirm this 
> behavior so we can be sure it isn't specific to our setup (XP 
> clients w/ Novell
> client32 4.9* and Netware 6.5 server):
> 
> 1) using any filepro database, take note of the "last 
> modified" timestamp of your key and index.A file.
> 2) start rclerk, select this database
> 3) choose "index selection" and a specific index
> 4) put any search criteria and start search
> 5) re-check the timestamp on the index file that was just used.
> 
> In theory, the timestamp in #1 and #5 should be the same, 
> since this was a read-only query.  In fact, if we take a copy 
> of the file before this process, and compare it byte for byte 
> against the one modified in step 5, there are no differences. 
> 
> Can anyone else verify this behavior on a different platform?
> 
> Thank you,
> Bob Haussmann
> Tabor Children's Services, Inc. 
> 

Bob,

I have been having an index problem on my development system with ODBC
5.6.06 also.  But not quite the same as you are seeing.

I have found 2 problems.
	1. A file open to IUA in one session and then going into dxmaint and
all defined indexes locked but those not defines able to be built.
	2. Index locks not being released when no one in a file.  In this
case all indexes a-z locked.

I have run into this problem while developing or modifying programs and need
to change the structure of or add a new index. 

This has been reported to fp support and they have asked me to send them a
file.  Since this can happen on any file, I need track the steps taken that
caused this problem.

Richard Kreiss
GCC Consulting