records not locking?

[scooter6 at gmail.com]

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


On Thu, Apr 17, 2014 at 12:18 PM, scooter6 at gmail.com <scooter6 at gmail.com>
wrote:

> Well, there aren't 2 lookups per se I'm using when doing this.......
> If I do DIRECTLY to the main data file through IUA, and then try to pull
> that same acct up in the input processing of the 'dummy' file that does all
> the protected lookups, I get the
> 'Wating for record to be unlocked...' message....
> If I reverse that, and pull up the record in the 'dummy' file that does
> all the protected lookups FIRST, and then use IUA directly to the data
> file, I can access the record with no problem?
> Hope that makes sense.....
>
>
> On Wed, Apr 16, 2014 at 3:46 PM, Kenneth Brody <kenbrody at spamcop.net>
> wrote:
>
>> On 4/16/2014 3:07 PM, scooter6 at gmail.com wrote:
>>
>>> Okay - after some more digging.....if I pull a record up directly in the
>>> filePro file itself and am in update mode...and then try to pull the
>>> account up in the processing that does all the lookups and protected
>>> lookups, I get 'Wating for 'mainfile' record xxxxxx to be unlocked'
>>> But, if I pull up the record in the processing that does all the lookups
>>> and what the employees use to access the main file, it lets me pull it up
>>> with no problem?
>>>
>>
>> What's difference about the lookup in the prc that waits for the lock,
>> and the one that doesn't wait?
>>
>> --
>> Kenneth Brody
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20140602/ec6aea43/attachment.html