report design / strategy

[boomer1974]

Hi Experts,

I am just looking for some different strategies for this one. I have about 10 reports listing various kinds of information, my manager has asked me to create a "dashboard" - basically a report that has summary info from 10 - 12 other reports. For example one report shows all purchase orders that are on our yard, the dashboard would only show a total not the line listing. how would you go about this. should I use sub reports, sql and combo boxes, etc. any ideas would be greately appreciated.

Boomer

 

[dRahme]

Hi, not knowing your table structures, sometimes a report with no recordsource works. Insert 10 or 12 text boxes for your summaries and use Dsum or Dcount. These work fairly well if you have a relatively small database and not a lot of data to sum or count through.

You can also construct queries for totals to do essentially the same thing.

I've never been a fan of large numbers of subreports. They cause headaches.

There are many ways to skin this cat. Its ease or comlexity depends to a degree on your table relationships.

Hope that helps

 

[TheAceMan1]

How ya boomer1974 . . . . .

Since your only talking totals, an [blue]unbound report[/blue] will do just fine. For your totals, have a look at the [blue]DSum Function[/blue] . . . .

See Ya! . . . . . .