Reports - Should they based on tables or queries?

[Jakboi]

Hello,

Looking for information on what reports should be based on tables or queries and the advantages or problems of doing the other.

I have some based on tables and Brian said that he beleives that supposed to be based on queries not tables.

Should it be queries, tables, both or doesnt matter?

Trying to figure out the importance and whether or not I should redo some of my reports and change them from tables to queries.

 

[Mile-O]

Queries. Always queries. The advantages are that you can sort the recordset, you can perform calculations within a query, you can limit the recordset. All things you can't do with a table.

 

[GaryPanic]

It does depend on what you are doing
a report on a table would be harder to filter on

whereas qry are easier to question/filter
and changing reports on qry and be very easy

example
qry1
has 4 fields in it that go to rep1
soemone wants a new report that has an extra field or two in it (they still want the orginal report)
so you could do a save as in the qry and in the report then change the source of the new named report to your nerw qry name

it does take a little time to wrap your head round this and this is a personal view - from expereince

 

[Jakboi]

Yea thanks for the information. This is my first real database and not sure if things are setup the way should be...appreciate it.

Thanks.