records not locking?

[Boaz Bezborodko]

On 6/3/2014 8:01 AM, filepro-list-request at lists.celestial.com wrote:
> Message: 1
> Date: Mon, 2 Jun 2014 12:19:50 -0400
> From: "scooter6 at gmail.com" <scooter6 at gmail.com>
> Subject: Re: records not locking?
> To: Kenneth Brody <kenbrody at spamcop.net>
> Cc: "filepro-list at lists.celestial.com"
> 	<filepro-list at lists.celestial.com>
> Message-ID:
> 	<CADpQzqOhybb6OyU+SfQWBuvLDHc50=uv4u0SV8Ys91tWdAW5Vg at mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> Okay - so here is what I did -- I double checked that all lookups to the
> main data file are in fact protected...but I noticed lots of occurrences in
> input processing for the dummy file that has all the screens etc that it
> uses to access the 'main data file' was full of 'write'
> statements....keeping in mind, this particular code was written before my
> time and has worked flawlessly for many years
> So recently it was noticed that two people could pull up the same record
> when in the 'dummy file' and only the person who first accessed the record
> - those changes would reflect, but not the 2nd person....so I made a copy
> of the input processing table....then went in and commented out all the
> 'write' statements in the input processing - now it's once again working as
> it was designed and I do in fact get the 'Waiting for .... record to be
> unlocked' message (as I should be getting and as I have been getting for
> many years)
> So I guess my question is, where/what is the potential of commenting out
> all the 'write' statements? I'm trying to decipher through the filepro help
> menu when a 'write' is needed
> The 'dummy' file that is used with multiple screens and does the protected
> lookups to the 'main' data file is used by the majority of our staff here -
> and they in fact will pull up records in various ways and make changes to
> data that is in the main data file......
> When can I do a 'write' or should I etc if they're doing protected lookups,
> etc?
> Just need some guidance I guess on when a 'write' is needed - without
> 'breaking' what's working again
> Thanks for any input
>
> Scott
> PDM
>
>

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.

You have to keep in mind that whenever you execute a WRITE command that 
the record in the file being written is now no longer protected.  If you 
want to do the WRITE and keep it protected then you'll need to 
re-execute the lookup.  If you don't specify a file it writes to all the 
open files and unlocks ALL the open records.

Boaz

---
This email is free from viruses and malware because avast! Antivirus protection is active.
http://www.avast.com