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



<Then I do READC S01 to determine subfile changes - the user may choose to
<place a one in one or many of the option fields or select F4=List to
prompt
<on a reason code.

<Has anyone got an example of how this is done.  I tried the SFLNXTCHG
<indicator but in all the reading I have found it to be quite confusing and
<am encountering multiple problems with not knowing which relative record
<number I am at when selecting F4 etc.  Basically I am in a big mess.  I
<think I have two separate problems here.  1)  I don't have the SFLNXTCHG
<keyword processing correct in my RPG and 2)  I don't know how to process a
<function key on a subfile.

<All I want to do is be able to do an F4 on the reason and have the code
<returned from a selection list to the correct subfile line selected from
<and if there are any errors - eg the user enters in the wrong code then
<that line is highlighted and not processed and the subfile is re-written
<showing the errors and removing those items already processed.

<Any help would be appreciated.

<Regards


<Kylea

<Kylea White

What a coincidence, I was trying to do the same thing last week.  I
realized that hitting F4 was not triggering a changed record so I changed
the program so the user was required to enter a special character to prompt
on a the subfile field.

I would rather use the F4.  How do I mark the record as changed when the
user hits F4?

Regards

John M. Bauman




As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.