Powerhouse Enhancement - ACCESS VIA, USING, IF

[Ken Langendock]

Sooooooooooooooo, I should have my answer in about 10 minutes or so???
 

  _____  

From: Deskin, Bob [mailto:Bob.Deskin at Cognos.COM] 
Sent: July 11, 2007 9:43 AM
To: Ken Langendock; mcl_systems at telus.net
Cc: powerh-l at lists.sowder.com
Subject: RE: Powerhouse Enhancement - ACCESS VIA, USING, IF


I suspect it wouldn't make much difference in development time for us. We'd
basically encapsulate everything generated from that ACCESS statement within
the IF. On the surface it looks straightforward, but I need to think about
side effects, inter-relationship with the FIND procedure, relational
database effects, etc.
 
Bob

-----Original Message-----
From: Ken Langendock [mailto:Ken at Langendock.com] 
Sent: July 11, 2007 9:40 AM
To: Deskin, Bob; mcl_systems at telus.net
Cc: powerh-l at lists.sowder.com
Subject: RE: Powerhouse Enhancement - ACCESS VIA, USING, IF


As an option to make the implementation easier you could make the REQUEST
and IF mutually exclusive.
I think it would be better in the long run to be able to specify both, but
for the example provided that would be enough.
 
Ken
 

  _____  

From: Deskin, Bob [mailto:Bob.Deskin at Cognos.COM] 
Sent: July 11, 2007 9:33 AM
To: mcl_systems at telus.net
Cc: Ken Langendock; powerh-l at lists.sowder.com
Subject: RE: Powerhouse Enhancement - ACCESS, VIA, USING, IF


Okay. I'll think on this one. As usual, no promises.
 
Bob

-----Original Message-----
From: Michael Lee [mailto:mcl_systems at telus.net] 
Sent: July 9, 2007 6:37 PM
To: Deskin, Bob
Cc: Ken Langendock; powerh-l at lists.sowder.com
Subject: Re: Powerhouse Enhancement - ACCESS, VIA, USING, IF


That's a great suggestion. I've had to modify the PATH and FIND procedure
several times for just such cases. 


Deskin, Bob wrote:


Interesting idea. Can I get a feel from the list as to how often people
modify the PATH procedure? And would something like this reduce that need?
Why else do you write your own PATH procedures?
 
We generate the PATH and FIND based on ACCESS statements (specified or
implied) for the PRIMARY file. The two procedures are tied together. The
generation is fairly basic at this point.
 
Bob

-----Original Message-----
From: powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com
[mailto:powerh-l-bounces+bob.deskin=cognos.com at lists.sowder.com] On Behalf
Of Ken Langendock
Sent: June 25, 2007 8:33 AM
To: powerh-l at lists.sowder.com
Subject: Powerhouse Enhancement - ACCESS, VIA, USING, IF


Here is a new enhancement targeted at reducing the number of times a
programmer has to hard code the PATH procedure.
 
FILE Users PRIMARY
  ACCESS VIA UserId &
       USING T-UserId &
          IF T-UserId NE " "
  ACCESS VIA UserId &
       USING UserId &
     REQUEST UserId
  ACCESS SEQUENTIAL
 
 
This new feature would generate a PATH statement similar to the following
thus removing the requirement of hard coding the PATH every time we want to
"override" the default path because of passed-in values or re-finding based
on a temporary item. etc.
 
PROCEDURE PATH
BEGIN
  IF T-UserId NE " "
     THEN LET PATH = 1
  IF PATH = 0
     THEN PROMPT T-UserId
...
END
 
 
Ken
 
 
  
 

 
     This message may contain privileged and/or confidential information.
If you have received this e-mail in error or are not the intended recipient,
you may not use, copy, disseminate or distribute it; do not open any
attachments, delete it immediately from your system and notify the sender
promptly by e-mail that you have done so.  Thank you. 

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