reporting madness

[tone]

hi ya,

i have set up a database with a section to print reports as per the requirments of the project. the project is to manage environemental weed management across a wide area. As the area is so large it has been broken up into infestation zones with sites nested within.

My problem relates to the production of reports. I have produced reports that will accumulate all works conducted within an infestation zone and give back associated data such as money spent, chemicals, area treated, etc.

Unfortunately the report doesn't have all the info in it, some sites have just slipped past the radar despite being assocaited with an infestation zone.

I checked the association by looking at the tables and i can see that these sites are within the infestation zone.

Starting to pull out my hair in frustratuion.

Is there any well known problem with reports and access 2000?

A

[nico5038]

Hard to tell from a distance, but the first thing that comes to mind is that you have missing data on the lowest level.
When there are no records for the detail level and you JOIN a main table with the subtable, then the missing rows will suppress the maintable rows.
Only a LEFT (or RIGHT) join will make them visible.
In the graphical query editor double click the connection line between your tables and chose option 2 or 3 making the required table "leading".

When still in trouble, posting the report's query might help.

Nic;o)

[tone]

Hard to tell from a distance, but the first thing that comes to mind is that you have missing data on the lowest level.
When there are no records for the detail level and you JOIN a main table with the subtable, then the missing rows will suppress the maintable rows.
Only a LEFT (or RIGHT) join will make them visible.
In the graphical query editor double click the connection line between your tables and chose option 2 or 3 making the required table "leading".

When still in trouble, posting the report's query might help.

Nic;o)

Thanks Nic,

I have looked into the relationships and it doesn't seem to be the problem all sites are referenced with an infestation zone. you mentioned posting the code of the query. This may be the problem as my report isn't based on a query rather just a compliation of data across tables, some subreports are based on queries as they need area calculations.

Is it necessary to base a report on a query? another intersting delima is that other reports i have created based upon species or site or agency as opposed to the infestation zone, all work fine, i really don't know whats happening

[NeoPa]

The report may be based on :
1 A table.
2 A QueryDef (Query)
3 Some SQL string.

Please post the following depending on above :
If 1, The layout of table giving field names and types.
If 2, The SQL of the QueryDef (found by designing query and switching to SQL view).
If 3, The SQL string itself.