FIND mode not working

[Darren Reely]

Mark,

I agree with your statement, BUT, the screen Syed is trying to port is a 
special case. The requested fields end up being used to fetch a common 
file via one of two keys (one dynamic) to gain the value required for 
the primary & secondary file access.

For what ever reason, the design of this screen is outside of the box, 
in a place Powerhouse coding can get confusing, especially by those who 
can't think outside of the Powerhouse box.

As for the code changes. The 'internal getparms' should be the PATH 
procedure. The 'do internal getparms' in the find procedure should be 
removed. 'RESET AT STARTUP' should be added to the TCOMPUTER field as 
mentioned by Richard.

Syed,

I hope the rest of your porting doesn't contain this type of coding. 
That would make me wonder how much bull dong (pun intended) is in the 
code. ;)

Good luck.


Darren


Mark Stewart wrote:
> Syed, 
>  
> It's always best practice to contruct your find procedure indirectly if 
> possible.  Since you are rather new to PH you might be tempted to dive 
> into those procedures and forget about the 4GL magic that PH gives you.  
> Access statements will dictate your code results.  If you are going down 
> the road of hard coding every single find and path then you're in for a 
> rocky road ahead.  Make sure your access statements match your find and 
> path logic.
>  
> Mark