records not locking?

[scooter6 at gmail.com]

So in looking at the fp.log file in /tmp -- I can see we've had these type
messages since day 1 so not sure how this plays into it
\r WARNING \r Assigning to lookup field without lock.
mainfile=NRcollect, loofile=NRdebtor, prc=input, line=664
\r WARNING \r Assigning to lookup field without lock.
mainfile=NRcollect, loofile=NRdebtor, prc=input, line=497
\r WARNING \r Assigning to lookup field without lock.
mainfile=NRcollect, loofile=NRdebtor, prc=input, line=498

But these lines aren't gotten to until after the lookup is done and it's a
protected lookup...so not sure what is happening here...or if it's even
related, since it appears we've gotten these lines for a really long
time.....



On Wed, Apr 16, 2014 at 11:28 AM, scooter6 at gmail.com <scooter6 at gmail.com>wrote:

> FWIW - If I go straight to the actual main file and get i update mode, I
> can also pull the record up in the processing I'm talking about......I know
> for certain we used to not be able to do that?
> Not good....
>
>
> On Wed, Apr 16, 2014 at 11:12 AM, scooter6 at gmail.com <scooter6 at gmail.com>wrote:
>
>> it's quite a big input prc table but basically it's a bunch of screens
>> with dummy fields that pulls up the records from this main file.....
>> I just can't understand why all of a sudden this is an issue and allows
>> this? I can't think it has to do with switching out the OS drives since I
>> didn't touch the filePro data
>> Could this be a permissions issue of any kind?
>>
>>
>> On Wed, Apr 16, 2014 at 11:07 AM, Kenneth Brody <kenbrody at spamcop.net>wrote:
>>
>>> On 4/16/2014 10:25 AM, scooter6 at gmail.com wrote:
>>>
>>>> Well this uses rclerk and we've never in the past (to my knowledge) been
>>>> able to access the same record in this rclerk program....
>>>> If I have the record 'directly' in update mode, and try to post a
>>>> payment
>>>> to it, then I get that message 'Record is being updated - access denied'
>>>> But I'm pretty shocked to see suddenly in this program two people can
>>>> have
>>>> the same record up at the same time and can make changes to it ,
>>>> etc....but
>>>> I do notice that if I'm the 2nd person to access it, and I make changes
>>>> to
>>>> it, it doesn't actually update the record? But if you're the first
>>>> person
>>>> to have it pulled up, those changes will take effect.....
>>>> Very strange....I have double checked that all my lookups to this main
>>>> customer file are 'protected' - I thought by doing that, you avoided
>>>> this
>>>> type scenario?
>>>> Am I wrong on that?
>>>>
>>> [...]
>>>
>>> Since you're apparently dealing with lookup, rather than the main file,
>>> can you please describe the processing steps you use to update that lookup
>>> record?
>>>
>>> Can you try a simplified prc which does just those steps?  Does it still
>>> allow two people in at the same time?  If so, contact fpsupport and arrange
>>> to send them files.
>>>
>>> --
>>> Kenneth Brody
>>>
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20140416/1b96b43a/attachment.html