Thank you, MJ. Unfortunately, neither hardcoding the branch location nor changing the location of the JOIN statement changes anything. I think what's happening is that, because of the WHERE condition, my revision is simply a very inefficient way of catching instances where a particular branch owns more than 1 copy of a particular item :-( Figured a subquery would work as a way to first restrict the results to records where Branch A owns at least one copy, & then to perform the search for duplicate records on the resulting subset. All best, Cab Vinton Plaistow Public Library On Wed, Aug 15, 2018 at 7:06 AM, MJ Ray <mjr@phonecoop.coop> wrote:
I'm a bit rusty on reports but could <<Library|branches>> be replaced by the code for your library (like 'MAIN' in the sample data) or m.homebranch IN ('BRA1','BRA2') if you want to match multiple branches?
And I suspect that LEFT JOIN may be position sensitive but I'm not sure what position would be best for either accuracy or performance.
I am probably misunderstanding how/why the attempted change didn't work.
Hope that helps, --
MJR http://mjr.towers.org.uk/ Member of http://www.software.coop/ (but this email is my personal view only)