>>I have a form that has several controls used to allow users to enter in search criteria. I build a WHERE clause based on what is entered by the user
>
>>In the past I've run the resultant data to a cursor because this data was not
>>to be updated. Now, I want to update the resultant data and would like to create a view here instead of the cursor. My question is, if my WHERE clause can constantly change based on user entries, how should a VIEW be constructed.

---

One approach (off the top of my head) would be to stick with a SQL SELECT with a completely dynamic WHERE clause - make sure that the field you select is the PRIMARY KEY, then use the results (if any) with SET KEY to restrict the records available to the User. This is similar to SET FILTER but should be much faster. The form can then use the fields in the underlying table with what ever buffering you prefer.

---

Just finished reading the on-line help for SET KEY and this will only work for a "range" of values - not a set.