Thanks Gary. Every advises I've receive so far go toward stored procedures and/or indexed view. I will look down that road.

Thanks again :)

>A fairly standard approach to this would be to create multiple stored procedures for each filter scenario you require. Whilst this may seem like a lot of stored procedures, its not really. We have hundreds of stored procedures on our system and they really are our preferred way to access data from not only VFP but from .Net too.
>
>To make life easier, you can quite easily source stored procedure code generators that you just point at the database and they will generate a full set of CRUD procedures that you can use as-is or modify to your liking. Also, studying generator ouput code is a good way to learn how how to write this type of stored procedure.