I'm guessing the answer to my OR / AND oddity was a syntax problem with the data type of the second field. It didn't matter when it was OR as the first option was true but failed when the AND was applied.