records not locking?

[Fairlight]

On Tue, Jun 03, 2014 at 09:10:24AM -0400, Boaz Bezborodko thus spoke:
> 
> When you have a simple command "WRITE" then Filepro writes all data to 
> all open files and then UNLOCKS THEM.  They are no longer protected.  If 
> you want to selectively free up a record you're working on (say a main 
> file for tracking the Invoice number and/or order number) then you 
> should execute the command "WRITE <filename>".  This will write the data 
> just for that file and then unlock it.

I don't recall it being officially documented that write unlocks a lookup.
I would consider that a big, glaring bug.  Close, yes...but write?  Nowhere
near as much.  That's not even sensible.  That's like saying write(2)
should automagically negate fcntl() or flock() in C.  It's insane.  The
whole purpose of locking is so that you have exclusive ability to
write...and write...and write some more, without interruption.

mark->
-- 
Audio panton, cogito singularis.