Mandy,

I wouldn't use parameterized views. There are just too many possible query combinations. I would build a SELECT statement on the fly and run it using macro substitution (or SQLEXEC() if your system is client/server).

>Hi all!
>
>I've got a very "wide" database which contains data on anything IT related in about 65 agencies. Our data ranges from hardware, software, peripherals, descriptions of internet systems or office automation systems, etc. We want to allow the users an interface to query the data and are looking for ideas on the best approaches to do so.
>
>We're going to look at our data and try to anticipate what the types of questions they'll want to ask, such as "Who is using hardware XYZ?" or "How many agencies are using software ABC?" and do have some historical information on previously asked questions.
>
>I'm thinking parameterized views and boolean logic would be ideal here, but am not sure what the best approach for this would be. Any ideas out there? (and am I being clear?)
>
>Many thanks!!
>
>Mandy