Hi all -

Thanks for the tip, I actually found a way around it a few minutes before you posted using a select case block in a formula and letting it make the decision rather than putting the logic right in the parameter field.  I also used strings instead of booleans... Just to see if I understand what's going on here though, originally I was adding the if statement as shown to the select formula.  It correctly selected producing wells but if you chose "no" it returned no results, because there was no else clause to handle anything other than "yes".  So naturally I was trying to figure out a way to say "else, select all" or something to that effect.  Eventually I realized I was thinking more in terms of a formula, not a select statement, which is why I went that route...

One other thing to consider is that John and Dell are using SELECT statements to implement the logic. This passes the work down to the server and produces much more efficient reports. If you are putting the logic in the report selection formula, there is a good chance that the report is doing the filtering and this can take much longer. You can check this by doing a Show Query and look to see if CR is passing the selection formula down to the server or whether it does it to all the data once it gets to the client side.