• Subject: Re: Setting a subfile record to changed with a function key
  • From: Dave Mahadevan <mahadevan@xxxxxxxx>
  • Date: Wed, 14 Jul 1999 19:40:16 -0400
  • Organization: Stoner and Associates


Besides the SFLCSRRRN which returns the record number on which the
cursor was as mentioned by other list mates,  investigate the SFLNXTCHG
keyword.   This keyword is used in the control format and usually
conditioned with an indicator.   You set on this indicator and update
the record.  Next time you READC the subfile, the record will get picked
up as if the user had done some work on the fields in the record.  This
is useful in checking for error correction on a field.  For example, the
user keys in a wrong data on a field and presses enter, you edit and
send the screen back, the user refuses to change the error and presses
enter again, now you have a problem because READC will skip this record
since there was no change.  But if you used SFLNXTCHG the READC will
pick this record even if the user did not make any changes.  HTH.

> Is there any way to get a subfile record to be marked as changed when a
> function key is pressed on a field in that subfile record
> I'm trying to do prompting on a subfile, but the only way to find out
> which subfile record the cursor was on when the function key was pressed
> seems to be to use the cursor location, RTNCSRLOC. Is there a better
> way?
Thank You.


Dave Mahadevan.. mailto:mahadevan@fuse.net

| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...

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

This mailing list archive is Copyright 1997-2019 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].