Solution found RE: Find procedure problems with Powerhouse 8. 39

[Deskin, Bob]

I'm not sure why this ever worked. Unless you retrieve a PRIMARY file record
in the FIND procedure, you'll never proceed to the POSTFIND or further.
Unless there's missing information. I notice that the files you list aren't
all mentioned in your procedures. Sounds like a bug that was fixed.

Bob Deskin              
PowerHouse Web Product Manager, Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 7268 FAX: (613) 727-1178
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA

-----Original Message-----
From: Sherry_Baillie@gov.nt.ca [mailto:Sherry_Baillie@gov.nt.ca]
Sent: Tuesday, October 29, 2002 6:37 PM
To: powerh-l@lists.swau.edu
Subject: Solution found RE: Find procedure problems with Powerhouse 8.39



No need for further responses - solution found.  

I changed the FIND procedure to a DETAIL FIND procedure and voila.

Interesting why this worked in pre 8.39 versions.........

Thanks to all respondents!

Sherry

-----Original Message-----
From: Sherry Baillie /YK /JUS 
Sent: Tuesday, October 29, 2002 3:52 PM
To: 'powerh-l@lists.swau.edu'
Subject: Find procedure problems with Powerhouse 8.39 


Help!  I'm having a difficult time trying to identify a problem I'm 
having with a quick screen since upgrading to PH8.39 for MPE.

The intention of the screen is to automatically display information to 
screen based on a passed parameter.  

With version 8.39 nothing is being displayed from the detail file.  I've 
included the files and applicable code below.  

Has anyone else come across the same problem and how do I rectify?

Thanks. 

Sherry 


Files:
file PERSON primary
     access via PERSON-IDX using p-person

file CHARGE alias CHARGE-SEC secondary
   access via PERSON-IDX using PERSON-IDX of PERSON

file DISPOSITION alias DISP-SEC secondary occurs with CHARGE-SEC
   access via CHARGE-IDX using CHARGE-IDX of CHARGE-SEC

file disp-obl   detail          occurs 6 noitems
   access via DISP-DETAIL-IDX using DISP-DETAIL-IDX of DISP-SEC

file disp-detail  SECONDARY occurs with disp-obl noitems
     access via disp-detail-idx using disp-detail-idx of disp-obl

> procedure FIND
> begin
>   for DISP-OBL
*W* FOR loop without missing option in FIND procedure.  Scrolling cache 
commands should be avoided.
>    begin
>     get DISP-OBL-REF via PERSON-IDX using PERSON-IDX of PERSON
>     get DISP-REF via DISP-DETAIL-IDX using DISP-DETAIL-IDX of 
DISP-OBL-REF
>     get SWORN-REF via SI-IDX using SI-IDX of DISP-REF
>     if INFO-TYPE of SWORN-REF ne "C"
>      then get DISP-OBL via OBL-IDX using OBL-IDX of DISP-OBL-REF
>    end
> end
> 
> 
> procedure postfind
> begin
>  let t-count = 0
>  while retrieving obl-chk via person-idx using person-idx of person
>  begin
>    let t-count = 1
>    break
>  end
>  if t-count = 0
>    then push next data
> end
> 
> procedure detail postfind
> begin
>  for disp-obl
>     begin
>   info = info-type of sworn-info now resp
>       if INFO-TYPE of SWORN-INFO ne "C"
>        then begin
>         let t-warrant = warrant-status of disp-detail
>         if filler30 of disp-obl <> " "
>           then do internal display-bail
>           else do internal display-disp
>         end
>      end
> end
> 



Sherry Baillie
Systems Analyst
Department of Justice
Government of the Northwest Territories


= = = = = = = = = = = = = = = = = = = = = = = = = = = =
Mailing list: powerh-l@lists.swau.edu
Subscribe: "subscribe" in message body to powerh-l-request@lists.swau.edu
Unsubscribe: "unsubscribe" in message body to
powerh-l-request@lists.swau.edu
http://lists.swau.edu/mailman/listinfo/powerh-l
This list is closed, thus to post to the list you must be a subscriber.

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.