>>>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.
>
>Ok, that worked great! I see that Viv had a similar idea using an object, but the cursor was easier for me implement right now. Thanks!

Class/object would be just a logical extension: custom class with a property 'CursorAlias' and a method 'BuildFilter'.