>>>I have a variable, m.FilterCondition, that is built as criteria is selected on the form. For example:
>>>
>>>m.FilterConditon = m.FilterCondition + " AND SomeValue = SomeOtherValue01"
>>>
>>>This works great until the same condition is selected again:
>>>
>>>m.FilterConditon = m.FilterCondition + " AND SomeValue = SomeOtherValue02"
>>>
>>>Now m.FilterCondition has both clauses, which causes problems. How can I ensure that I have a good conditional variable?
>>
>>Most likely, you could check if 'SomeValue' is already in the condition and replace that part of the string instead of adding to it. You could keep list of conditions in the cursor, so checking could be easier.
>
>Interesting. So, you mean to create a cursor, add a record for each condition, then search for the condition to determine if it should be used or not? I could have a flag on each record that detemines whether to use it or not. Rebuild the filter each time based on that rather than using a variable that just keeps getting added to. I like it. That is what you meant, sort of, right?
Yes, I do it sometimes this way. Cursor is also convenient if you use filter condition through multiple forms. Certainly, it assumes that you don't use private datasessions.
Edward Pikman
Independent Consultant