Hi All,
I have a many-to-many association between the tables 'Specification Detail' and 'Drawing Detail'. We have to pay a certain amount each year to have our specifications reviewed, so to make life easier for us and to save money on reviewing unnessesary specifications (ones that are not currently associated to a drawing, ones that have been manually marked as obsolete, or ones that have already been reviewed in the last 12 months), i'd like to print a report that lists all the specifications that DO need reviewing.
So far I have a query that pretty much does this for me, but my problem is with duplicates. Because one spec can be associated to many drawings (and vice versa), my query would list the same spec many times depending on how many drawings it belonged to.
Is there any way to prevent the same spec appearing more than once either at the query level or the report level? I have a feeling that the solution is fairly simple but I can't get my head around it.
I have attached a scaled down version of my database, with just the relevent tables, queries and report.
Any suggestions would be appreciated.
Jonesy
I have a many-to-many association between the tables 'Specification Detail' and 'Drawing Detail'. We have to pay a certain amount each year to have our specifications reviewed, so to make life easier for us and to save money on reviewing unnessesary specifications (ones that are not currently associated to a drawing, ones that have been manually marked as obsolete, or ones that have already been reviewed in the last 12 months), i'd like to print a report that lists all the specifications that DO need reviewing.
So far I have a query that pretty much does this for me, but my problem is with duplicates. Because one spec can be associated to many drawings (and vice versa), my query would list the same spec many times depending on how many drawings it belonged to.
Is there any way to prevent the same spec appearing more than once either at the query level or the report level? I have a feeling that the solution is fairly simple but I can't get my head around it.
I have attached a scaled down version of my database, with just the relevent tables, queries and report.
Any suggestions would be appreciated.
Jonesy