>>>>>I am looking for better logic to my input statement.
>>>>>I have 10 input boxes representing 10 diff fields which the user enters values into as many as he likes to narrow down his search.
>>>>>the more textboxes filled out, themore narrow his search becomes.
>>>>>Then I must set a filter using my screwy logic unless someone has a good idea for me.
>>>>>Thank you !
>>>>
>>>>I have a procurement status system that does just that. There are 18 fields to filter on. So what I did was set up a view and have a parameter for each possible field that would be entered. They are all character fields so I would initialize the parameters in the form to "". Then if the user entered data into a filter field then the parameter would be set, if they did not then a "" parameter matches all records. I found this to be a slick solution to the query screen that requires many fields to be entered. The view would bring back all the records filtered on what the user entered. HTH
>>>
>>>Brett, What I need to do is isolate the records into a cursor or table and work with them from there.
>>
>>My solution isolates the query into a view that I work with, it is updateable and indexed. So I guess I dont understand the question.
>
>Without using views( I haven't used them), I need to have a resultant dbf, from the large filter.

Will the result table be updated or just used to report with?