Yes, precisely: it's syntactically fine. This isn't the most optimal solution, but that is another matter. Formally, SQL optimises
(a or b) and (c or d) and (e or f)
just as well as
(a and b) or (c and d) or (e and f)
but the query design grid really only manages the second structure correctly (as this is the most frequent criteria structure used by average users).
Cheers!
(°v°)