However, I have a serious problem with putting in 200 and some odd parameters for the view to work. 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.

>>That works as long as the user is constantly querying looking at data, making adjustments and doing more queries. My idea is to let the user sort on ANY column in the grid simply by clicking on it. I would have to create too many indexes to do that (close to 240).
>>
>>>Once you get datat selected into a cursor, you can make the cursor RW and index it.
>>>
>>>select ... into cursor crsTemp
>>>use dbf() agin in 0 crsMyCursor
>>>use
>>>select crsMyCursor
>>>index on ... tag ...
>>>
>>>When you close the cursor, the CDX is removed from disk as well.
>>>
>
>Why not re think your data collection.
>
>Looks like a ot of data and look up descriptions? If so Query the data in the form of a view, and relate look up descriptons. This will save time in your query and give you a better handle on what you are working with.
>
>In a view you can index on all the columns in a no data on load and then bring in the records via a requery().
>
>Just loking at if from a different perspective.
>
>Now your grid header click events could just change the order and go!
>
>__Stephen