@ud and @ub updated

[Dennis Malen]

I now went one step further. I did everything I did below plus put an "end" 
on the first line of auto proc and deactivated @entsel in "input". Problem 
still repeated itself.

Dennis Malen
516.479.5912
----- Original Message ----- 
From: "Dennis Malen" <dmalen at malen.com>
To: "Bruce Easton" <bruce at stn.com>; <filepro-list at lists.celestial.com>
Sent: Monday, April 09, 2007 6:07 PM
Subject: Re: @ud and @ub updated


> As a further update I went into "input" and at the top of the processing
> placed an "end" on the first line. I then put the @key code and moved it
> right under the "end" line.
>
> The error still occurred. There is something that causes the record to go
> into update mode and effectuate and esc esc.
>
> If you did not have any processing in input and you pressed esc esc it 
> would
> update the @ud and @ub.
>
> Dennis Malen
> 516.479.5912
> ----- Original Message ----- 
> From: "Dennis Malen" <dmalen at malen.com>
> To: "Bruce Easton" <bruce at stn.com>; <filepro-list at lists.celestial.com>
> Sent: Monday, April 09, 2007 5:40 PM
> Subject: Re: @ud and @ub updated
>
>
>> Bruce and Ken,
>>
>> I tried the lookup - in another file and it did not change @ud and @ub.
>> There must be something I have in "input" which causes the record to go
>> into
>> update mode when I am taken to the new record to view.
>>
>> Obviously, when lookup - transfers me to another record in the problem
>> file
>> there is processing in "input" that causes it to update and therefore
>> change
>> the two fields.
>>
>> Do either of you have any idea of what type of processing in "input" 
>> would
>> cause the entire "input" processing to be activated. Now by the process 
>> of
>> elimination, thanks to the list, this is what appears to be happening.
>>
>> Where do I now start to look in "input" processing????
>>
>> I remember years ago there was a filepro article that was written that
>> indicated that when doing any updating it should be done after @entsel so
>> that if someone was running a report the record in update would not 
>> effect
>> the running of the report.
>>
>> Just as a reminder, I deactivated auto proc and @entsel and the problem
>> still persisted.
>>
>> Dennis Malen
>> 516.479.5912
>> ----- Original Message ----- 
>> From: "Bruce Easton" <bruce at stn.com>
>> To: <filepro-list at lists.celestial.com>
>> Sent: Monday, April 09, 2007 3:45 PM
>> Subject: RE: @ud and @ub updated
>>
>>
>>> Dennis Malen wrote Monday, April 09, 2007 3:23 PM:
>>>>
>>>> Bruce,
>>>>
>>>> I did deactivate auto prc and @entsel. Neither solved the problem.
>>>>
>>>> Dennis Malen
>>>
>>> OK - this is starting to go beyond cocoa puffs.  But, Dennis - in
>>> reviewing your older posts I  just noticed that you said back on Friday:
>>>
>>>>>I never had this problem in 4.8. I am on AIX and am not sure whether
>>>>>that could be the problem.
>>>
>>> AIX?? does anyone out there speak French???
>>>
>>> Ken - could the AIX be different than other platforms for 5.0?
>>> Also, Dennis - what level of 5.0 are you on?
>>>
>>> Bruce
>>>
>>> Bruce Easton
>>> STN, Inc.
>>> _______________________________________________
>>> Filepro-list mailing list
>>> Filepro-list at lists.celestial.com
>>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>>
>>>
>>>
>>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>
>>
>>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>