Static:
I was simply suggesting that the OP format the return value of his calculated field as any other boolean field would be formatted.
We don't disagree about what needs to be done, only about how, perhaps.
My suggestion was that EXPLICIT formatting (as for example use of CBool) is needed because the default IN HIS SITUATION was not Boolean, but BYTE INTEGER, the underlying datatype for the typecast of Boolean. That is how he saw the -1 when he was expecting TRUE. It was caused by asking the wrong question (using the wrong format, if you prefer).
Is it possible that the OP erred in the command he gave by omitting a formatting option? Probably. Is this a bug in Access that it didn't stop him? Damfino, but maybe not.
We have to remember that VBA is Visual BASIC for Applications, but that the acronym is multi-layered. The language specification for BASIC is a bit loose because BASIC is "Beginner's All-purpose Symbolic Instruction Coding." The original thrust of the language was to be forgiving, unlike ADA or PL/1, because it was targeted towards beginners who were more likely to make errors. So VBA might not have complained, it simply did an (invisible) typecast and showed -1 in a context where that seemed to be the right answer even though it was confusing.
As to whether the OP knows what Google is, there we are again probably on common ground. Except that we should remember that for some newer folks, they don't know enough yet to ask the right question. I remember how TERRIBLY noobie I was for my first few posts on this forum until I learned to do a search and not give up if it happened that my first couple of keywords produced nothing useful. That's why I try to show some patience to the new members who ask a question that might be answerable on Google. But this particular question might have been a bit harder to trace down because the reason is a bit more obscure.