Be careful of the OR check against the database then. If the field changes to NULL the TR portion will not evaluate to true but the check against the database will.
Dave -------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) <[email protected]> To: [email protected] <[email protected]> Sent: Tue Oct 02 21:57:09 2007 Subject: Re: Filter Problem I did not realize that the TR. value would = $NULL$ just because it was not being modified, when it already contained a value. It makes sense now that I think about it. The 'AssignedConfigTech' can possibly be set to $NULL$, but in that case I do not want the filter to fire. Andy L. Mayfield Sr. System Operation Specialist Alabama Power Company Office: 8-226-1805 ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Shellman, David Sent: Tuesday, October 02, 2007 8:04 PM To: [email protected] Subject: Re: Filter Problem You need to be careful that the AssignedConfigTech can't be set to NULL. If it is the TR.AssignedConfigTech will resolve to NULL. Dave -------------------------- [EMAIL PROTECTED] (Wireless) ----- Original Message ----- From: Action Request System discussion list(ARSList) _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
