>This is not true. If you want to build a QBF interface that allows users to select as many or as few filters from x number of fields, then you need a class like this. You can not code it straight in line, because you don't want irrelevant filters in your WHERE clause.
>
>I have had need for a class like this many times, but have never yet taken the time to build a generic one, I have just handled it per situation so far.
>
>I, too will be watching this thread for ideas.

Yeah, the last one I did I just had a bunch of nested IF statements that handled it. Now I've got to do it again (this time with 4 potential filters), and possibly more. I had hoped the SQL class in the class library here would handle it, but it only de/constructs a SQL statement, not building the WHERE clause. I guess I'll have to put some thought into this.