>That's why I was issuing the select statement in the first place: because getting a parameterized view to work with all those parameters was going to be more difficult than dynamically changing the WHERE clause in an SQL statement.

I don't think he meant a parameterized view. I think the idea is to create a view from the SQL statement that you created. This would essentially be the compilation of data that i mentioned in my other reply. You could have the environment load the view with no data, then index the fields with no data (which happens quickly because it's just setting the definitions) then requery the data into the form. I don't know how well that will work with 240 indexes to build while the data comes in...

Start with: Create View as Sele (your Select statement)
Then simply make the user wait when they ask for an index that doesn't already exist. This project is coming to you from Marketing isn't it? They tend to ask for crazy sorts/views, and draw conclusions from the oddest places. <g>

Disclaimer: Any similarity or likeness to any actual marketing department is accidental and the opinions expressed herein are gathered through limited observations of a statistically insignificant number of marketing departments. Generalizations were made by extrapolation and the margin of error increases proportionally to the degree of generalization. (I should've been a lawyer!)