Well there has been extensive discussion over the last few days on the subject.
TR and DB are prefixes that can be used in filter qualifiers to check for changes. 'TR.Field' is a transactional value associated with a field. It can be used to detect when a change happens to a field. It can give seemingly inconsistent results at times though. 'DB.Field' references the value of the field in the database. 'Field' is basically the value of a field when the record is created or modified. These can be used in differing qualifiers with filters. To check that a value has changed most folks that have been around for several years will use 'Field' != 'DB.Field' If the filter should only trigger if the field is not NULL then use 'Field' != $BILL$ AND 'Field' != 'DB.Field' Dave -------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) <[email protected]> To: [email protected] <[email protected]> Sent: Thu Oct 04 16:58:23 2007 Subject: TR, DB, and nothing Can someone explain the difference between the following: 'FieldName' 'TR.FieldName' 'DB.FieldName' Are there other prefixes out there that may be of use? If the DB. is what I think it is, it's something I've asked for, but was told didn't exist, so I have had to do extensive coding around it (Creating a dup field, setting it via work flow, comparing 2 field values, etc). Thanks! M _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
