yes, there are times, when the entire record is empty. The ID exists meaning it's valid, but there has been no data associated with it yet.
It was acceptable that 1. the record could be empty (but the @ID exist) essentially, this is the same as <1> being "" 2. the record could contain <1> and not be the same as @ID 3. the record could contain <1> and be the same as @ID 4. the record not exist (then a whole other set of checks come into play) It's just coincedence the <1> and @ID would be the same value, however they are not the same field, so it's not that I'm duplicating the @ID into <1>. > -----Original Message----- > From: [email protected] [mailto:u2-users- > [email protected]] On Behalf Of Kebbon Irwin > Sent: Monday, October 11, 2010 1:58 PM > To: [email protected] > Subject: Re: [U2] Stumped with TRANS... > > > I don't mean to belabor this point, but unless your *entire* record is > empty, doing the the trans with a full record requrest - > TRANS('FNAME',@ID ,-1,'X') - you should only have a null returned if > the record does not exist. I use Unidata; is Universe any different? > You can do something like a DCOUNT to ensure that if <1> is emplty, > there are other attributes in the record.... > > Last post, I promise. > > Cheers, > > Kebbon > _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
