@ud and @ub updated
Dennis Malen
dmalen at malen.com
Fri Apr 6 15:36:44 PDT 2007
I double checked the auto proc and there is no write command. Furthermore,
the @key only possesses those lines and has an end statement.
Again, I never had this problem in 4.8. I am on AIX and am not sure whether
that could be the problem.
Dennis Malen
516.479.5912
----- Original Message -----
From: "Bruce Easton" <bruce at stn.com>
To: <filepro-list at lists.celestial.com>
Sent: Friday, April 06, 2007 6:10 PM
Subject: RE: @ud and @ub updated
> Kenneth Brody wrote Friday, April 06, 2007 6:00 PM:
>> To: Bruce Easton
>> Cc: filepro-list at lists.celestial.com
>> Subject: RE: @ud and @ub updated
>>
>>
>> Quoting Bruce Easton (Fri, 6 Apr 2007 17:54:01 -0400):
>>
>> > Kenneth Brody wrote Friday, April 06, 2007 5:36 PM:
>> > > To: Dennis Malen
>> > > Cc: filepro-list at lists.celestial.com
>> > > Subject: Re: @ud and @ub updated
>> > >
>> > >
>> > > Quoting Dennis Malen (Fri, 6 Apr 2007 17:21:02 -0400):
>> > >
>> > > > I have @ud and @ub in the screen. When I am taken to that record it
>> > > > updates both without ever going into update.
>> > >
>> > > Umm... You're in @key processing, which _is_ in update mode. If
>> > > your @key doesn't take you into a screen, then you simply come out
>> > > of update mode when you hit the END statement. By the time filePro
>> > > redraws the screen at the end, you have updated that record, and so
>> > > @UD/@UB are updated to reflect this.
>> [...]
>> > Ken - I'm not seeing that on 5.014. If I just end right after the
>> > lookup -, my @ud and @ub are unchanged - on the screen or when I go
>> > back to the browse. I wouldn't think you are in update mode from @key
>> > unless before the end you do a screen or popup command. I even tried
>> > a display command (by itself) and it still did not change @ud/@ub.
>>
>> It's possible that his code modifies a field, forcing the modified
>> record to be written out.
>>
>> You are definitely in update mode in @key processing.
>>
>> I would have to check what happens in @key if you make no changes to
>> any real fields. It may be that the record does not get written out
>> when @key processing ends if no changes were made in @key.
>>
>
> I tried for kicks video sync and that didn't change them either.
> I DO remember recently writing something that did a "popup -,<sc>"
> type command and it did update the record even though, I think,
> there were only dummy fields on the popup and it subsequently did
> not (by my code) write any individual field to the record it was
> standing on.
>
> Yes, he must either have something after what he supplied (or maybe
> a write in automatic.
>
> Bruce
>
> Bruce Easton
> STN, Inc.
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>
>
More information about the Filepro-list
mailing list