Designer Proc Nodata

[Deskin, Bob]

As far as I can recall, the difference is in the manuals. The 8.1 manual is
correct.

Bob Deskin              
Senior Product Advisor, Application Development Tools, Cognos Inc.
bob.deskin@cognos.com (613) 738-1338 ext 4205 FAX: (613) 228-3149
3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA


-----Original Message-----
From: Thomson, Martyn EDUC:EX [mailto:martyn.thomson@gems1.gov.bc.ca]
Sent: Wednesday, June 23, 1999 12:42 PM
To: 'POWERHOUSE Listserv'
Subject: RE: Designer Proc Nodata


Thanks for the explanation Bob.  
Now I dig deeper I see the 8.1 manual I downloaded from the Cognos website
and quoted has the qualifier "...if the number is also a field ID-number",
added to the statement "The NODATA option is ignored for numbered DESIGNER
procedures."  The hardcopy manual (v.7.10) has no qualifier.
Is there a difference in the way the 2 versions handle designer procedures
or just a difference in the manuals?
Guess I should read the right manual, eh? 

Martyn Thomson
Ministry of Education, B.C.
Football's not a matter of life and death... it's more important than
that. Bill Shankly


> -----Original Message-----
> From: Deskin, Bob [mailto:Bob.Deskin@Cognos.COM]
> Sent: June 21, 1999 7:21 PM
> To: 'POWERHOUSE Listserv'
> Subject: RE: Designer Proc Nodata
> 
> 
> The NODATA option doesn't mean anything for numbered DESIGNER 
> procedures. I
> haven't checked the exact wording in the manual but it sounds 
> mistaken or at
> a minimum misleading. If you have a data screen (i.e. not a 
> menu), then
> numbered designer procedures are expected to deal with data 
> or be links to
> subscreens. Therefore QUICK assumes that you should have data 
> already on the
> screen in order for them to be executed. Granted that's not 
> always valid,
> but that's the way QUICK has always been (barring the occasional
> inconsistant glitch). I don't think this is any different in 
> 7.10E vs G.
> 
> Bob Deskin              
> Senior Product Advisor, Application Development Tools, Cognos Inc.
> bob.deskin@cognos.com (613) 738-1338 ext 4205 FAX: (613) 228-3149
> 3755 Riverside Drive P.O. Box 9707 Stn. T, Ottawa ON K1G 4K9 CANADA
> 
> 
> > ----------
> > From: 	Thomson, Martyn 
> EDUC:EX[SMTP:martyn.thomson@gems1.gov.bc.ca]
> > Sent: 	June 21, 1999 6:14 PM
> > To: 	'POWERHOUSE Listserv'
> > Subject: 	Designer Proc Nodata
> > 
> > Hello,
> > I have a designer procedure called "64" with the NoData 
> option.  It calls
> > an
> > inquiry screen, but it wont execute giving me the message 
> "There is no
> > data.".  If I give it an alphabetic name e.g. "PEN" it 
> works fine, with or
> > without data on screen!
> > 
> > The manual states that a number OR a name can be used as a designer
> > procedure identifier.
> > It also states that the nodata option is ignored for 
> numbered procedures
> > if
> > the number is also a field ID-number, but this is not the 
> case in this
> > instance - my highest field number is 14.
> > 
> > We've just upgraded to 7.10G1 on OpenVMS and Oracle Rdb 
> 7.0., (and removed
> > the previous version 7.10E1) so I have no easy way of 
> checking is due to
> > the
> > upgrade or not.
> > Can anyone test this for me and/or offer a suggestion as to what is
> > causing
> > this?
> > 
> > Martyn
> > = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
> = = = = = = =
> > =
> > Subscribe: "subscribe powerh-l" in message body to
> > majordomo@lists.swau.edu
> > Unsubscribe: "unsubscribe powerh-l" in message to 
> majordomo@lists.swau.edu
> > powerh-l@lists.swau.edu is gatewayed one-way to 
> bit.listserv.powerh-l
> > This list is closed, thus to post to the list, you must be 
> a subscriber.
> > 
> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = 
> = = = = = = =
> Subscribe: "subscribe powerh-l" in message body to 
> majordomo@lists.swau.edu
> Unsubscribe: "unsubscribe powerh-l" in message to 
> majordomo@lists.swau.edu
> powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
> This list is closed, thus to post to the list, you must be a 
> subscriber.
> 
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.
= = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
Subscribe: "subscribe powerh-l" in message body to majordomo@lists.swau.edu
Unsubscribe: "unsubscribe powerh-l" in message to majordomo@lists.swau.edu
powerh-l@lists.swau.edu is gatewayed one-way to bit.listserv.powerh-l
This list is closed, thus to post to the list, you must be a subscriber.