Re: Conceptual subfile question

Yes Booth - you can also do it that way - but you’re not answering the same question then.

Comparing before/after display images tells you whether _your_ operator made changes on the screen.

Comparing previous/current disk images tells you whether somebody else changed the record while you were waiting for the operator to decide what they donated to do.

You can of course combine both techniques. I should have mentioned that the article was dealing with not holding prolonged locks on the database but the same basic “image” technique works just fine as a means of avoiding hidden fields.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

On May 3, 2016, at 4:21 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

Hey, I like that! Have never used eval-corr; I guess I did not understand what it did. Thanks Jon.

A question, mostly to see if I understand what is happening:
Lets suppose the data record has 15 fields and the program is dealing with only 7 of them. When I do the compare-for-changes-at-another-workstation I care only about those 7; changes in the other 8 fields do not affect my changes. Therefore don't I want Dim(2) on DisplayRec, not CustRec?

Which leads to other questions. However, My first goal is to understand what you are showing us.

On 5/3/2016 2:22 PM, Jon Paris wrote:

Boy you guys like to make it complicated!

Read this for a much simpler approach http://www.itjungle.com/fhg/fhg030315-story01.html

The example there is for a single record update but the exact same method can be used when handling subfiles. The only time I would ever consider using hidden fields for this purpose in a subfile is if that “subfile” were a web page and I was using to hold state information.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related questions.