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



I can give a suggestion as to a "different" way to do it. Whether or not
it's better depends....

Here's one way I'd do it.

I'd have.....

A message subfile for all error / informational messages to be displayed on
line 24. 

A standard screen format to display function keys available. This usually
has information on lines 22 and 23. Make sure this is created with the
overlay keyword so the message subfile will work

A subfile control record & subfile to fill the rest of the screen, lines 1
thru 21 including the "more" line. Within the control record I'd have an
input field above each field within the subfile that is "selectable". (This
is where you're parms come from.) I then use SQL to build your subfile
according to what the user keys in the selection fields. Build your dynamic
SQL statements, read the cursor and write to your subfile accordingly. Once
you have data in the subfile you can use standard options (2=change,
4=delete) processing or simply allow the user to change the data in the
subfile. If you use option processing you pop a window for create/ change /
delete. etc. if that's what you really want to do.

I have example DDS and source. It's really very simple if you have an
understanding of dynamic SQL processing. If you want it I'd rather send it
direct instead of to the list. 

Let me know.


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Tony Carolla
Sent: Tuesday, December 21, 2004 1:10 PM
To: RPG programming on the AS400 / iSeries
Subject: The best approach...


I have a lookup inquiry module I am building, and I am not sure what
the best approach is.  I usually build this type of application with a
parameter format, which allows them to put in their search criteria,
then a sfl/sflctl format pair that shows them the results.  To choose
different parms, they simply press F12, and are taken back to the parm
format, yadda yadda yadda, until they press F3

But I would like this one to be different.  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.

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?

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


-- 
"Enter any 11-digit prime number to continue..."
-- 
This is the RPG programming on the AS400 / 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 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.