ah yes, thanks for pointing that out. Initially I had the LEFT OUTER JOIN in the outer query. So if anything I at least cleaned this up a lot and made it more effecient.
The problem is still there though, but I've finally nailed down the actual problem! The Union query by itself actually...
That does sound like whats happening. I've never done much with SQL before, but while it's easy enough to pick up as you go along, I'll overlook things like this. At first glance though putting in an INNER JOIN seems to have the same effect, but I'll keep looking at it from that angle...
I'd certainly hope it isn't a case of myself messing up some simple logic, that would be bad. But it's a bit more comlpicated than that.
Basically, the query by itself gives me several hundred rows of 'groups', of 8 combinations of counts, binary-wise 000(=0) to 111(>0). It actually is...
I'm working on an SQL query for Access, and have come across an unusual problem. Basically, simplifying names to keep it more generic, the table I'm creating will look like this:
Name |A1Count|A2Count|A3Count
------------------------------
GroupA| 0 | 3 | 4 |
GroupB| 2 | 0 |...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.