force a FIND?

[Joe Boyle]

I'm reluctant to say this, but won't 'push find' simply re-run the path proc
requesting the user to enter record key values ? I think this is what this
lister wants to avoid.

Regards, Joe.


-----Original Message-----
From: powerh-l-admin@lists.sowder.com
[mailto:powerh-l-admin@lists.sowder.com] On Behalf Of Martin McDonough
Sent: 22 April 2005 16:49
To: Ken@Langendock.com; roger32909@bellsouth.net
Cc: powerh-l@lists.sowder.com
Subject: RE: RE: force a FIND?

Roger, what Ken has listed is they way to do it. You'll need a 'reset at
startup' on the temp item though.

Martin.

-----Original Message-----
From: Ken Langendock [mailto:ken.langendock@rogers.com] 
Sent: 22 April 2005 16:32
To: roger32909@bellsouth.net; Martin McDonough
Cc: powerh-l@lists.sowder.com
Subject: Re: RE: force a FIND?

Ok let me clarify this for you.

screen a

temp t-xyz-key char(??)

file XYZ primary
access via xyz-key usign t_xyz-key 
access via xyz-key request xyz-key

procedure x ; can be procedure entry/find/whatever
begin
  run screen b
  push find ; invokes once this procedure ends
  let t_xyz-key = xyz-key of XYZ
end

procedure path
begin
 if " " ne t-xyz-key
    then let path = 1
    else prompt xyz-key
end

procedure postfind
let t_xyz-key = " " ; clear it out for next find



If you want more clarification....send me the screen
code.

Ken

--- roger32909@bellsouth.net wrote:
> Already tried PUSH FIND.  This still required user
> intervention to Find the updated record.
> 
> REFRESH does not do a FIND.
> 
> The PRIMARY file XYZ record is NOT passed to the
> called screen.
> In the called screen, the file XYZ is a DESIGNER
> file. 
> 
> Agree with you, Martin, but unfortunately the
> subscreen is called from many other screens, so it
> is not possible to pass the record.
> 
> > 
> > From: "Martin McDonough"
> <martin.mcdonough@rosebys.com>
> > Date: 2005/04/22 Fri AM 10:17:25 EDT
> > To: <roger32909@bellsouth.net>
> > Subject: RE: force a FIND?
> > 
> > If possible, the correct way to do this would be
> to pass the primary
> > file 'XYZ' to the subscreen and display the field
> from the 'passed' file
> > on the subscreen.
> > 
> > By putting 'REFRESH' on the field statement of the
> main screen, after
> > the update is done in the subscreen and you return
> to the main screen,
> > the value will be automatically refreshed.
> > 
> > Regards
> > 
> > Martin McDonough
> > 
> > -----Original Message-----
> > From: powerh-l-admin@lists.sowder.com
> > [mailto:powerh-l-admin@lists.sowder.com] On Behalf
> Of
> > roger32909@bellsouth.net
> > Sent: 22 April 2005 15:07
> > To: powerh-l@lists.sowder.com
> > Subject: force a FIND?
> > 
> > OpenVMS 7.3  PH 7.10.G1
> > 
> > We have an old screen that works this way:
> > 
> > The PRIMARY file in the main screen is XYZ.
> > The user has the option of calling another screen.
> > If the user goes to the subscreen, file XYZ is a
> DESIGNER file in that
> > screen and an XYZ field is updated.
> > 
> > But when the return is made to the original
> calling screen, the original
> > record is still displayed without the updated
> field.
> > 
> > To be sure, the screen designer displays a message
> telling the user that
> > data has changed and to perform a(nother) FIND to
> see the updated data.
> > 
> > Is there a way to perform this FIND for the user
> so that when the RETURN
> > is made, the updated data is displayed on the
> screen without user
> > intervention?
> > 
> > -- 
> > 
> > = = = = = = = = = = = = = = = = = = = = = = = = =
> = = =
> > Mailing list: powerh-l@lists.sowder.com
> > Subscribe: "subscribe" in message body to
> > powerh-l-request@lists.sowder.com
> > Unsubscribe: "unsubscribe &lt;password&gt;" in
> message body to
> > powerh-l-request@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.
> > 
> > Disclaimer: 
> > 
> > This message contains information that may be
> privileged or confidential and is intended only for
> the person to whom it is addressed.
> >  If you are not the intended recipient, you are
> not authorized to read, print, retain, copy,
> disseminate, distribute, or use this message or any
> part of this message.
> >  If you receive this message in error, please
> notify the sender immediately by using the reply
> option and delete all copies of this message.
> > 
> > Rosebys Operations Ltd.
> > 
> > WWW.ROSEBYS.COM
> > 
> > 
> > 
> 
> -- 
> = = = = = = = = = = = = = = = = = = = = = = = = = =
> = =
> Mailing list: powerh-l@lists.sowder.com
> Subscribe: "subscribe" in message body to
> powerh-l-request@lists.sowder.com
> Unsubscribe: "unsubscribe &lt;password&gt;" in
> message body to powerh-l-request@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.
> 

-- 
= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.sowder.com
Subscribe: "subscribe" in message body to powerh-l-request@lists.sowder.com
Unsubscribe: "unsubscribe &lt;password&gt;" in message body to
powerh-l-request@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.