force a FIND?

[roger32909@bellsouth.net]

OK, Ken, you are right again.
This screen already had a custom path procedure:

PROCEDURE PATH
   BEGIN

...
    IF T-CNUM NE " "
	THEN LET PATH = 1
    ...

So, I removed the extra LET statement and everything still works fine.

Thanks again,
Roger
> 
> From: Ken Langendock <ken.langendock@rogers.com>
> Date: 2005/04/25 Mon AM 10:14:03 EDT
> To: roger32909@bellsouth.net,  Martin McDonough <martin.mcdonough@rosebys.com>
> CC: powerh-l@lists.sowder.com
> Subject: Re: RE: force a FIND?
> 
> Glad to here your success. 
> 
> I could be wrong...:), but I think the LET PATH = 1
> statement does nothing. As soon as you restart the
> PATH procedure... It should reset the Path to 0. 
> 
> Enjoy.
> Ken
> 
>  --- roger32909@bellsouth.net wrote: 
> > Thanks Ken and Martin.
> > 
> > I added this at the end of the designer procedure
> > that calls the subscreen:
> > 
> >    ;Upon return, find record again because it may
> > have been updated;
> >    ;display and recompute remaining (see postfind
> > proc)
> > 
> >     LET T-CNUM = T-CNUM-PASS           ;load a temp
> > with desired key value
> >     LET PATH   = 1	                            ;this
> > PATH finds the record via key using T-CNUM
> >     PUSH FIND
> > 
> > I added this to the POSTFIND procedure:
> > 
> >     LET T-CNUM = " "	                           
> > ;blank it for next (F)ind
> > 
> > And now the screen works as I believe it should: 
> > The updated record is displayed to the user with no
> > intervention.
> > 
> > Roger
> > 
> 
>