Reports

[Fitz]

Hi All

Can you design a form, to apply different filters from one query, and print different reports, rather than have one query for each report.

Thanks

Fitz

 

[Corticus]

You could,

But why?

Having lots of queries should have little to no negative impact on your database. They take up almost no memory, as they are just stored SQL expressions, maybe a few lines at most.

I see a lot of reluctance to use multiple queries in a db, but I don't think its necessary. If its easier to make one query per button on your form, and have each button print a report based on that button's query, go for it. You should notice no difference between this method and your proposed method. Actually, using a specific query for each report might be faster, since you will be running the simplest possible query for each report, not one cumbersome query designed to do everything.

My 2 cents - pile those queries up. Never delete them, and if you need 20 simple queries or one fancy one, go with the simple 20.

There are, of course, exceptions to this, like a search by form query, for example, where it is easier to have one dynamically generated query produce a set records as opposed to querying a query that queries a query that queries a query (etc) depending on what information the user wishes to search on.

HTH,

 

[Fitz]

Thanks for the quick reply

I will stay with the many querys.

Do you have an example of a form query.

Thanks

Fitz

 

[Corticus]

Sure,

Here's a great example:
http://www.theillumni.com/httpdocs/posts/multicriteria.zip
you can download from my site...

I found this here:
http://www.access-programmers.co.uk...3d40b0&threadid=36145&highlight=multicriteria
there's some additional info here,

HTH,