Problem in screen design

[Peter Bateman]

Hi All: 

  
My idea is the reverse of the technique where you remove the optional

   from the get of the secondary to display only those primary
records which have a 

   corresponding secondary file. A failed get on a non optional
secondary raises

   an error condition.

 

   An error in the FIND sequence goes back to
the next primary record if there is one

   otherwise back to the action field.



From:- http://public.dhe.ibm.com/software/data/cognos/documentation

         
/docs/en/powerhouse/8.4g/QD.pdf



   "Error Handling in the FIND Procedure

   If an error occurs during the execution of this procedure, 

   QUICK backs up to the last GET verb for the PRIMARY file. 

   If no such verb exists, QUICK prompts the screen user in the
Action field,

   without displaying any retrieved data."

    For example:-


     file  apmisumi

     select  if source-code = "632654450"
and gm-part <> "    12844161" &

             
 and (flag-905="P" or flag-905="C") 

 

     file  apmisumi secondary alias bad_part 

     access via APMISUMI-KEY &

                   using
doc-char +"632654450" + "    12844161" 

 

 

     
Procedure Find

     
Begin

          
Get apmisumi

          
Get  bad_part optional

           If
NOT NEWRECORD of bad_part

            then
error " "

     
End

 

 

Jay tried
it and got it working. Good work, Jay!
Regards, 
Peter


 		 	   		  
_________________________________________________________________
IM on the go with Messenger on your phone
http://go.microsoft.com/?linkid=9712960
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.sowder.com/pipermail/powerh-l/attachments/20100318/48fdb613/attachment-0001.htm