Retrieving and displaying records by non-indexed fields on
Quick screens
roger32909 at bellsouth.net
roger32909 at bellsouth.net
Mon Jul 18 10:18:14 CDT 2005
The S for select in action field works OK when each field to be (S)elected has it's own ID.
These screens display some 10 fields horizontally on each line so the fields have a common ID and S(elect) does not work.
The indexed subfile solution works fine in some cases, especially when the records must be sorted in some order different from main file indexes.
>
> From: "Joe Boyle" <atla38 at dsl.pipex.com>
> Date: 2005/07/17 Sun PM 03:47:36 EDT
> To: <roger32909 at bellsouth.net>, <powerh-l at lists.sowder.com>
> Subject: RE: Retrieving and displaying records by non-indexed fields on Quick screens
>
> When you run the 'S' action field command, quick first prompts for indexed
> retrieval key values and then prompts for id's of fields for which values
> can be entered which will be used as additional filters. I strongly suspect
> that this is the case for both RMS indexed files and indexed SUBfiles.
>
> When using indexed SUBfiles as primary files I have seen only one
> requirement, which is that at least the dictionary part must exist before
> the subscreen ( which will read the subfile) option is selected by the user
> - but this is easily achieved by running a dummy quiz which selects no
> records, but which creates a blank dictionary SUBfile part.
>
> You are on VMS which means that a logical can be created to easily identify
> a unique subfile for any given user and time.
>
> Regards, Joe.
>
>
> -----Original Message-----
> From: powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com
> [mailto:powerh-l-bounces+atla38=dsl.pipex.com at lists.sowder.com] On Behalf Of
> roger32909 at bellsouth.net
> Sent: 17 July 2005 04:08
> To: powerh-l at lists.sowder.com
> Subject: Retrieving and displaying records by non-indexed fields on
> Quickscreens
>
> Restrictions: PH 7.10G on OpenVMS with no relational database, only RMS
> files. The project manager declined request for additional indexes.
>
> The requirement is to allow user to retrieve and display records by at least
> 5 fields. Three are indexed and can be handled by normal ACCESS statements
> with default PATHs & FINDs. But the fourth is a date range and the fifth is
> a non-indexed field.
> The primary file will occur 15 times and the user may drill down by using a
> designer procedure 01 to run a screen displaying more details.
>
> This system already has 2 screens with multiple prompts and a convoluted
> SELECT statement, custom PATH & FIND procedures to handle screen displays of
> data retrieved on non-indexed fields. Of course there is no sort/order, but
> it works. A new screen is supposed to follow this pattern. But I wonder if
> there may be a simpler solution.
>
> For example, I have seen (and used) permanent indexed subfiles (re-filled by
> QTP or QUIZ) to sort & display records on QUICK screens retrieved on
> non-indexed fields. The tradeoff is a slight delay for the QTP/QUIZ run.
>
> I have not tried, but assume one could also declare several versions of the
> same file using aliases with ACCESS/SELECT statements and passing the
> retrieved data to occurring TEMPs for screen display.
>
> Would like to hear of other possible solutions to similar requirements.
>
> --
> = = = = = = = = = = = = = = = = = = = = = = = = = = = =
> Mailing list: powerh-l at lists.sowder.com
> Subscribe: "subscribe" in message body to powerh-l-request at lists.sowder.com
> Unsubscribe: "unsubscribe <password>" in message body to
> powerh-l-request at lists.sowder.com
> http://lists.sowder.com/mailman/listinfo/powerh-l
> This list is closed, thus to post to the list you must be a subscriber.
>
>
More information about the powerh-l
mailing list