I agree that the values are probably null.
However Access boolean fields can only be true or false (unlike those in SQL Server)
So that must surely mean you are using an unbound checkbox whose value you haven't set!?!
Hi Frothy
I wondered that which was why I mentioned SQL Server.
From memory, null boolean fields in SQL Server tables are treated as false UNTIL you try & run update queries involving those fields.
Doing that creates the dreaded write conflict error
Once I realised that issue, I always set a default value for boolean fields in SS so null values are never an issue again
I think that's how it worked, yes. It's been years since I discovered that and just started ensuring that bit fields could not contain null values, so my memory of the precise mechanics has grown a bit fuzzy.