I've got a database of projects which has worker's time and materials tables, separate tables and linked via a project number field.
I've created a project summary report that shows details of the project and brings in two subreports - one for any relevant time and one for any relevant materials for each project number - and I sum up the totals. The subreports run from queries which pull the data from the three tables.
I have a problem with the materials subreport in that for one particular project number, 111, it also calculates the values from project number 110 (but it only shows the materials for 111). If I alter the value of the materials for 110 it reflects in the total for 111.
It only happens for this one particular project number, and for the life of me I can't figure out why - running the query on its own only brings up the correct values, running the subreport on its own brings up the correct values and total, but running it within the main report it brings up the wrong total.
Can anybody shed some light on possible reasons for this?
The job number field is anumber field, long integer, with 0 decimal places.
I've created a project summary report that shows details of the project and brings in two subreports - one for any relevant time and one for any relevant materials for each project number - and I sum up the totals. The subreports run from queries which pull the data from the three tables.
I have a problem with the materials subreport in that for one particular project number, 111, it also calculates the values from project number 110 (but it only shows the materials for 111). If I alter the value of the materials for 110 it reflects in the total for 111.
It only happens for this one particular project number, and for the life of me I can't figure out why - running the query on its own only brings up the correct values, running the subreport on its own brings up the correct values and total, but running it within the main report it brings up the wrong total.
Can anybody shed some light on possible reasons for this?
The job number field is anumber field, long integer, with 0 decimal places.