|
Michael,
I have tried your suggestion. After the user presses a command key on a
particular record, I set the value of the hidden field associated with
SFLRCDNBR in the DDS to what's in the hidden field associated with
SFLCSRRRN in the DDS (which contains the record number for the record the
user selected), and then an EXFMT of the subfile control record happens
(there is a WRITE of a different display format immediately before this
that displays command key text). Still positions to the first record of
the subfile. No DSPATR(PC) in play for this subfile.
Looking at the definition of SFLRCDNBR, it says that using this keyword
displays "the page of the subfile containing the record whose relative
record number is contained in this field". So am I interpreting it wrong
that it will actually position it to the SPECIFIC subfile record? Because
there are only 3 records in the entire subfile, so if you take this
definition literally, positioning the cursor to the first record is
technically displaying the page of the subfile that contains the record the
user selected. Maybe I've got the wrong keyword for positioning on a
specific record?
Bill
On Tue, Mar 17, 2015 at 11:54 AM, <MichaelQuigley@xxxxxxxxxx> wrote:
Bill,
Sorry I've been away from the list for a few days. What you're trying to
do should work. There are a couple things that've bit me or coworkers when
we've tried this.
1) You say you're "...moving the field value that goes along with
SFLCSRRRN to the SFLRCDNBR field and updating the subfile." Do you mean
you're updating the individual subfile record or rewriting the subfile
control record with the new SFLRCDNBR value? You need to rewrite (i.e.,
update) the control record. You do not need an input capable field. You do
not need to do a DSPATR(PC).
2) A prior DSPATR(PC) can mis-position the cursor. One common problem is
to leave the indicator for DSPATR(PC) turned on and update the individual
subfile record before updating the control record. That or defining PC on
another field in the subfile record without any indicator.
Those are the big ones. Have you got this working yet?
Michael Quigley
Computer Services
The Way International
www.TheWay.org
"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 03/13/2015 09:59:09
AM:
----- Message from Bill Howie <blhowie66@xxxxxxxxx> on Fri, 13 Mar<rpg400-l@xxxxxxxxxxxx>
2015 09:29:08 -0400 -----
To:
"RPG programming on the IBM i (AS/400 and iSeries)"
that
Subject:
Positioning cursor on a subfile record
Hello all,
I'm having the darndest time getting this to work. I have a subfile
has several fields. The first is an output field. Our program logicthis
dictates that if the cursor is on a particular line in the subfile (at
output field) and F1 is pressed, logic occurs to do things with thatF1
specific record. That all works fine. In some cases the user hitting
on a particular record is an error. I'm generating an error messagethat
displays at the bottom of the screen and THAT all works fine. I'd liketo
position the cursor on the subfile row that the user hit F1 on in thisthe
situation but no matter what I try it doesn't seem to work. I've got
subfile set up with the SFLRCDNBR(CURSOR) keyword and also theSFLCSRRRN()
keyword and I'm moving the field value that goes along with SFLCSRRRN to--
the SFLRCDNBR field and updating the subfile. STILL doesn't work. Does
it have to do with the fact that it's an output field I'm trying to
position it on? Because I've made it an input field and that's not
working either. Any suggestions? Thanks!
Bill
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.