v processing question

[Jeff Harrison]

Joe Chasan wrote:
> 
> On Mon, Jun 21, 2004 at 10:35:54AM -0400, Kenneth Brody wrote:
[snip]
> > The record is not locked during the sort/select process, therefore
> > updates are not allowed.  Yes, there are ways to force the record to
> > be modified, but you're asking for trouble, just like modifying an
> > unprotected lookup.  (Though you can probably get away with it if
> > you make sure to not use the "-u" flag.)
> 
> i wonder if fp tech would actually ever let us control the 
> locking status 
> of file - e.g. new commands
> lock(filename) (use "-" for current)
> and
> unlock(filename) (use "-" for current)
> 
> for times like this as well as @key, @entsel, certain lookups where
> we want to write without losing / releasing lock, etc.
> 

Ken was referring to the -u flag which controls file locking - not record
locking.  For example per Ken's suggestion if you were to run a *report
process without the -u flag and there was someone in inquire/update/add on
the file that you were trying to update, then filepro would not allow you to
run your process - you would get a filepro error.

Jeff Harrison
jeff.harrison at epixweb.com

Author of JHExport and JHImport - The fastest and easiest ways to generate
code for filepro exports and imports.  Demos available upon request.