Re: Conceptual subfile question

I don't think so Jon. Using a hidden field containing a DS, or multiple hidden fields (one for each field) when dealing with subfiles makes life easier since you don't have to define a separate array that mirrors the subfile. And using the same technique for single record formats just keeps things consistent. I can still keep my main logic clean by shuttling the hidden field logic off to a sub-procedure for testing whether things are changed or for populating the hidden fields. Main logic stays clean, and what I am doing with those hidden fields is explicitly defined.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx


-----Jon Paris <jon.paris@xxxxxxxxxxxxxx> wrote: -----
To: Rpg400 Rpg400-L <rpg400-l@xxxxxxxxxxxx>
From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
Date: 05/03/2016 03:22PM
Subject: Re: Conceptual subfile question


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 &#8220;subfile&#8221; were a web page and I was using to hold state information.


Jon Paris

www.partner400.com
www.SystemiDeveloper.com

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

Your response is a great response and is well said.

I'd add this: I define a data structure made up of the input-capable fields on the screen and also define a field named OrigFields. When I write the subfile record I also populate OrigFields, which becomes a hidden field in the subfile record.
That provides:
- an easy two-field compare,
- allows an easily implemented F5-Refresh,
- an easy way to check if any updated fields were changed at another work station in the interim between the unlocked read and the locked chain.

On 5/3/2016 8:04 AM, Mark Murphy/STAR BASE Consulting Inc. wrote:

... To determine if a record is changed, I simply keep hidden copies of every input field, and compare the saved value to the input field. Those hidden copies are loaded with the subfile record, and do not change until I save the subfile record out to the database. ...

--
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.