× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



John/Jeff,

The symptom is this: I have a 3-record subfile. I'm wanting to position
the cursor to record 2, because that's the record that the user was sitting
on and tried to do a function that we aren't allowing (in this case they
use F1 to try this function). Doesn't seem to matter what I try, it
always positions the cursor to record 1.

It shouldn't matter that it's an output-only field that I'm trying to
position on should it?

Bill

On Fri, Mar 13, 2015 at 2:05 PM, John Yeung <gallium.arsenide@xxxxxxxxx>
wrote:

What are the symptoms of the "not working?" Where does the cursor
wind up when you press F1? Is the proper page of the subfile showing?

Do you perhaps have an unwanted CSRLOC keyword that is overriding
other methods of positioning?

I would think there is some way to get SFLRCDNBR(CURSOR) to work. But
if you can't, and you're willing to manage the exact cursor position
yourself (that is, position by screen coordinates rather than subfile
record/field), you could potentially use CSRLOC yourself.

John Y.
--
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 thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.