If you could also cover the differences between True, <> False, False, and <> True in query criteria, that would be great.

I was working through the Assets Web Database (the sample template on Access 2010), and one of the queries uses <>False to return records. I could not understand why (e.g., why not just use, True?). On some forum somewhere, a post said that <> False is used so that the table is not resorted, but I don't know if that is true or <>true. I do know that when I tried to adapt this query to a real dataset, it *did* resort for some reason and it did mess up my data.

I would love to see this issue and others like it addressed.

Cant wait to take this course!

---

Reply from Richard Rost:

The real reason why you would use FALSE and <>FALSE (not FALSE) is because you only want to deal with checking one value. Now, with Access, if your database is set up correctly and you're using a BOOLEAN type (Yes/No) then your value can ONLY be True or False. However, in some other programming languages like VB or C++, if you don't properly TYPE your variables, you could end up with empty strings ("") or even Null values. So it's better to check for TRUE and NOT TRUE, or FALSE and NOT FALSE, because there are other "bad" values that can creep in. But, again, if you are using Access and you have your variables properly defined as BOOLEANS, then that shouldn't be an issue.