Re: The best approach...

[Scott Klement <rpg400-l@xxxxxxxxxxxxxxxx>]

> I want to have a top section of the screen that allows them to enter 
> search criteria, and a bottom section of the screen that allows 
> selection of items in a sub-file of the entries that are found.  Entry 
> of either a character on a subfile line takes them to a detail screen 
> format, and entry of new parameters in the top section rebuilds the 
> subfile in the bottom section.

Here's what I'd do:

a) Put the entry fields in the SFLCTL record.

b) When the program receives control back from the EXFMT of the control 
record, first use READC (or whatever method you prefer) to find the 
selections in the default subfile, and process those.

c) Next, check to see if any changes were made in the input of the SFLCTL 
record, and if so, process those.


> I started thinking of using window-bordering, and making a top format
> window for entry, a middle format window for the subfile control
> record, a lower middle format window for the subfile, and a bottom
> format window for F-key and instruction line.  But I am not sure, if I
> use the selection parms and exfmt the subfile, and the user changes
> the top format window selection parameters, will I receive these in
> the DSPF field buffers?  Or will only the subfile records change?

I don't recommend that approach. It'll mean that you have to write 
additional records to the display, and then read additional records. 
Aside from that, it'll work exactly the same as putting the input fields 
in the SFLCTL record.

So, that's what I'd do... I'd just put the inputs in the SFLCTL record and 
be done with it.

If you really want to use separate windows, it should be possible to first 
write them all out, and then read them all in.  Even though you perform 
multiple READ op-codes, it won't wait for input multiple times, only once. 
(As long as you wrote them all out before the first read, that is...)

But, IMHO, that's not very intuitive.  I'd much prefer to see them all in 
the SFLCTL record.

> Is there a better way to do this?  Can you have input fields in the
> SFLCTL format?

Yes, you can.  It's just like any other record in that respect.