Perhaps you might be better of without the boolean field anyway,
as JET has some problems with yes/no data type. Details in:
Why I stopped using Yes/No fields
at:
http://allenbrowne.com/NoYesNo.html
Allen, your example of the outer join bug makes no sense. You have a
join between company and employee and group on CompanyID, which is
available in your Employee table. Thus, you don't need to have a
join at all. Your example should group on the Company field instead
to make any sense.
Of course, I don't see the point of the outer join at all, except to
produce a list of all companies with the counts for invited/not
invited. But that makes no sense, as you could have people with no
company who are invited (i.e., self-employed).
And you're asking Jet to summarize Null fields *if* there are no
employees for a particular company. But if there aren't, then, well,
why include them in the resultset at all?
In other words, I think your example is artificially constructed to
produce an error. I've in all my years never encountered this
problem and I use just this kind of structure all the time,
including the Boolean fields.
