Just ( 'TR.AssignedConfigTech' != $NULL$ ) would work, right? On 10/2/07, Atul Vohra <[EMAIL PROTECTED]> wrote: > > ** > ( 'AssignedConfigTech' != $NULL$ ) AND ( 'DB.AssignedConfigTech' != ' > TR.AssignedConfigTech') > > When that field is not changed then 'TR.AssignedConfigTech' = $NULL$ while > 'DB.AssignedConfigTech' != $NULL$ > thus the filter fires. > > This qual should work > > ( 'AssignedConfigTech' != $NULL$ ) AND ( 'DB.AssignedConfigTech' != > 'AssignedConfigTech') > > Regards > Atul > > ----- Original Message ----- > From: "Mayfield, Andy L." > To: [email protected] > Subject: Filter Problem > Date: Tue, 2 Oct 2007 18:04:16 -0500 > > ** > > OK, I am stumped. I have a filter firing that should not be. > > > > I have a filter that sends a notification based on the qualification > statement: > > > > ( 'AssignedConfigTech' != $NULL$ ) AND ( 'DB.AssignedConfigTech' != ' > TR.AssignedConfigTech') > > > > If I am reading the statement correctly, the filter should not fire unless > the 'AssignedConfigTech' is changed. > > > > This filter is firing when the form is saved without a change being made > the 'AssignedConfigTech' field. > > > > There is a value in the field, so it's != $NULL$, but no change is being > made to the field so it should not meet the criteria. > > > > *Andy L. Mayfield* > *Sr. System Operation Specialist* > *Alabama Power Company* > *Office: 8-226-1805* > *Cell: 288-9140* > *SoLinc: 19140* > > > __20060125_______________________This posting was submitted with HTML in > it___ > > > __20060125_______________________This posting was submitted with HTML in > it___ >
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
