You'll need to describe all of that in much more detail--particularly how you have designed your layout and on what table you have based it.
It's possible that you need only perform a find that omits records for the other report.
OK there are three main tables the first is the condition report table this has a UUID along with all its fields, then there is the 2 tables I have already mentioned that both have there own UUID along with the FK ID of the condition report tale they are DB details table and Circuit detail table
The circuit details table is the one been used in my print layout
All the condition report fields i have put in a leading grand summary (this seems to be working fine) then I have a sub-sumary for the DB Details that is using the circuit details table and it sorts by the DB FK field in the circuit details then under that is the body that shows the circuits details sorted by DB
The omit records idea is what I thought I might need but I'm not sure how to execute it at the moment I have a button that runs a script
Enter browse mode
Go yo layout [print report]
but not sure how to omit records by the UUID of another report
Are these your relationships? (but possibly with different field namds)
DB Details>-----Condition Report------<Circuit Detail
Condition Report::UUID = DB Details::Report FK
Condition Report::UUID = Circuit Detail::Report FK
For an explanation of the notation that I am using, see the first post of: Common Forum Relationship and Field Notations Explained
If you perform your script from a layout based on Condition Report, you can use Go to Related Records to go to your report layout and only pull up the Circuit Detail records linked to your current record on the Condition Report layout.
Go To Related Record [Show only related records; From table: Circuit Detail; Using layout: "Print Report" (Circuit Detail) ]
Not quite I have the following
condition report UUID=DB Details::condition Report Fk
db details UUID = Circuit details:: DB Details FK
Condition report UUID = Circuit details 2 ::condition Report FK
because if the DB details isn't linked to circuit details then the circuit detail records go for all DB's
ok I have tried the script to no avail so I have taken a screen shot of my relationships I sure i have messed up somewhere
sorry I have missed out the test results table as I was trying to make it as simple as i could to explain. it may be easier if i combine the test results with the circuit details but these the condition report (if I can get it to work) would be used over and over and the circuit details mostly stay the same but the results need to be changed every time I test so my thinking was to keep the details separate so I could just change the results I am hoping to turn this into an app for the Ipad so that i can use it on site and may be put it out on the app stare as a stand a loan but one step at a time I think LOL Thanks for all your help be the way
ok I got the script to work setting the print layout table to circuit details table and then using go to related records it is working I think
I still require a bit of help though do I have the relation ships correct do you think
I see no need to use two pairs of match fields between the Condition Report Details and circuit details records.