If the field's value has not changed then the TR value is NULL while the DB value may not be NULL
Fred From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Tommy Morris Sent: Wednesday, April 14, 2010 3:47 PM To: arslist@ARSLIST.ORG Subject: Re: TR vs DB sanity check please ** I understand how Rick put it that the TR is implied so you don't have to specify it but why would including the identifier cause an erroneous result? From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Thad K Esser Sent: Wednesday, April 14, 2010 3:44 PM To: arslist@ARSLIST.ORG Subject: Re: TR vs DB sanity check please ** Tommy, In some situations, your version will evaluate to true, even though nothing changed. To truly detect if a value changed, its best to use: 'AssignedToTech' != 'DB.AssignedToTech' Thad Esser Remedy Developer From: Tommy Morris <tommy.mor...@radioshack.com> To: arslist@ARSLIST.ORG Date: 04/14/2010 01:39 PM Subject: Re: TR vs DB sanity check please Sent by: "Action Request System discussion list(ARSList)" <arslist@ARSLIST.ORG> ________________________________ Instead of Runif: 'AssignedToTech' != 'AssignedToTech' Make it Runif: 'TR.AssignedToTech' != 'DB.AssignedToTech' -----Original Message----- From: Action Request System discussion list(ARSList) _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"
