RE: subfile?

Mike,

I think I know what you are talking about.   you are handling the paging
yourself, by loading one page, and sensing the page up/page down and
clearing and reloading the sfl accordingly.

if this is the case, make SLFSIZ 1 more than SFLPAG.   since you are
handling the paging (up and down always returns control to the program), it
shouldn't matter.

also, you will have to load 2 pages at a time, due to the fact that a page
size is the number 'unfolded', so 'folded' (or visa versa, i always get
that mixed up) would actually show twice the number of lines.

and another problem you'll have is that since you are handling the paging,
once you re-exfmt your sflctl, it will revert back to it's natural
fold/drop state, regardless of where it was when they paged.

to fix this, you will need to trick the subfile by toggling the condition
for SFLFOLD and SFLDROP using both keywords with opposite indicators - code
it like this:

                CF19
N10             SFLDROP(CF22)
 10             SFLFOLD(CF22)

F19 would be described to the user as the 'fold/drop' command key.  f22
would never be used, it's only to satisfy the syntax of the keywords.

when they press F19, control is returned to your program and you would
execute the following code:

c              if      *inkt
c              eval    *in10 = (not *in10)
c  ...... go back to your exfmt and redisplay
c              end

this technique will keep the 'fold/drop' state consistant when they page.

does this make sense?  If i'm not being clear, let me know.

hth,

rick

------original message--------
In my case there can be well over 100,000 records, and I believe the
expanding subfile will blow at 9999.   That's why I was hoping to find a
way around the sfldrop issue on a page at a time subfile.  Just hoping
their was something I was missing.