David and Dawn, 'Description' isn't a variable but can easily be made into one as David suggests...
Thanks to both... > -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Dawn Oakes > Sent: Friday, June 10, 2005 11:13 AM > To: RBG7-L Mailing List > Subject: [RBG7-L] - RE: 7.5 Report Question > > Claudine, > > If you have the variable defined, then I wouldn't think you would need > to GET the textvalue PROPERTY. The variable already exists (you said it > was a variable label.) > > Dawn > > -----Original Message----- > From: Claudine Robbins [mailto:[EMAIL PROTECTED] > Sent: Friday, June 10, 2005 11:42 AM > To: RBG7-L Mailing List > Subject: [RBG7-L] - 7.5 Report Question > > I'm having fun designing a new report in 7.5 which contains a sub-report > as > follows: > > Label: stop | > Variable Label: Concatenated fields TO and SHIPPER Db memo: DESCRIPTION > > All on one line. > > When there is data, this is what is printed: > > Stop | LAFAYETTE - SMITH INDUSTRIES 3 BOXES OF TOOLS > > Many times, however, the stop doesn't have a description and when that > happens, I want to suppress printing the whole line. > > After carefully studying RRBYW10 EepsInReportBands, I have: > > Put the three objects of my sub-report on region3 (visible checked) and > (1) given it a component id of region3, and (2) given a component id to > DESCRIPTION of stopdesc. > > Now, on a "before generate" eep in the detail band, I want to test the > value in DESCRIPTION: > > GETPROPERTY stopdesc TEXTVALUE 'vstopdesc' > IF vstopdesc IS NULL THEN > PROPERTY region3 VISIBLE FALSE > ENDIF > RETURN > > Unfortunately, it suppresses the line even when there is a value for > DESCRIPTION... > > I find no documentation of GETPROPERTY command in reports... > > TIA, > > Claudine :)
