FIND mode not working

[Mark Stewart]

Syed,

I just wanted to point out that that you shouldn't jump

in to the find procedure on every screen.  I know some guys love the 

the control but it goes against the grain enough that after a 

while it can turn a system to crap.  There have been many 

times where I've had to do it but I'm trying to point

since your a newbie that it's not the best practice.  I've been

places where people thought that if you didn't code the find 

procedure by hand you couldn't find anything period :).  That 

went for the update producedure too.  Darren made reference to the

PowerHouse box.  I think it's a lot easier to be out of it then 

in it.

 

You should only start coding paths and finds if like Darren said

your're 'outside the PowerHouse box'.  With time you'll see what he

means.  I'm not a big Axiant guru so I'm not sure how much it 

really inherited from PH as far as best practices go.  

I'm more on the BI side these days so my family won't starve 

to death on the streets.

Mark

Dear Mark, Joe,I'm new to PH and AXIANT as well.But I have a person with PH knowledge with me.The application that I am migrating is a complete application runningon MPEIX. I'm not the one who wrote it and the customer (our sisterconcern)  has none of the programmers who wrote it. I am justmigrating it with the Axiant Migration tool which is doing much of thework, except for such things as OCCURS fields in a table, STRUCTURESand FIND procedures as such.I'm not writing any fresh code. Do you mean I have to change all theseFIND procedures? In that case, what change should I probably make tothe code file that I have attached on the other thread ? Can u throwsome more light on what you mean by 'construct find procedureindirectly'?Thanks & Regards,SYED.On 7/21/05, Mark Stewart <markstewart at consultantsclub.biz> 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> --> = = = = = = = = = = = = = = = = = = = = = = = = = = = => Mailing list: powerh-l at lists.sowder.com> Subscribe: "subscribe" in message body to> powerh-l-request at lists.sowder.com> Unsubscribe: "unsubscribe &lt;password&gt;" 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.> > >

---------------------------------


   Previous message: FIND mode not working 
   Next message: FIND mode not working 
   Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] 

---------------------------------
More information about the powerh-l mailing list

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20050722/d6b98daa/attachment.htm