PenWin wrote:

>> Hi Pepak!
>>
>> There's nothing wrong with mixing approaches. I agree that two or three
>> parametres would be about maximum if you wanted to make the best
>> possible query in all circumstances. But what about making sure that at
>> least one indexed field is specified completely so that the index can be
>> used?
>>
>
> Hi!
>
> It could be a good compromise indeed. My data could support this approach
> reasonably well. I'll give it a try.
>
> Thanks,
>
> Pepak
>

I like the set approach.

But if the problem is to handle the complexity of too many diferent
queries when one uses to many parameters, you could write a small app
that generate the SP body for you make all possible combinations.

The problem will be the 64kb limit size of the SP.

My approach is to generate the filter condition on the fly based on
supplied fields (at application side), all access are done trough views
that hide the joins between tables and so on.

see you !

--
Alexandre Benson Smith
Development
THOR Software e Comercial Ltda
Santo Andre - Sao Paulo - Brazil
www.thorsoftware.com.br