|
On May 3, 2016, at 3:43 PM, broehmer@xxxxxxxxxxxxxxx wrote:
Jon,
The week that article came out our shop tried it, liked it and have never
looked back. We stopped using hidden everything and just use likerec
and eval-corr for inquiry and maintenance. Love it!
Bill
From: Jon Paris <jon.paris@xxxxxxxxxxxxxx>
To: Rpg400 Rpg400-L <rpg400-l@xxxxxxxxxxxx>
Date: 05/03/2016 02:23 PM
Subject: Re: Conceptual subfile question
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx>
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
On May 3, 2016, at 3:09 PM, Booth Martin <booth@xxxxxxxxxxxx> wrote:fields on the screen and also define a field named OrigFields. When I
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
write the subfile record I also populate OrigFields, which becomes a
hidden field in the subfile record.
That provides:work station in the interim between the unlocked read and the locked
- an easy two-field compare,
- allows an easily implemented F5-Refresh,
- an easy way to check if any updated fields were changed at another
chain.
every input field, and compare the saved value to the input field. Those
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
hidden copies are loaded with the subfile record, and do not change until
I save the subfile record out to the database. ...
--mailing list
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
To post a message email: RPG400-L@xxxxxxxxxxxxquestions.
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
--
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.
"CONFIDENTIALITY NOTICE: This e-mail transmission (and/or the attachments accompanying it) contain confidential information belonging to the sender. The information is intended only for the use of the intended recipient. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution or the taking of any action in reliance on the contents of the information is strictly prohibited. Any unauthorized interception of this transmission is illegal under the law. If you have received this transmission in error, please promptly notify the sender by reply e-mail, and then destroy all copies of the transmission."
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.