Why?? Why does that have to be a failure?? Why can't Firebird just
ignore it??

Is there any switch to turn off this behaviour??

(I've got some immensely complicated query generation code which, it now
appears, can occasionally include a common table expression in the query
that isn't actually used anywhere. I've now got to fix that code to be
extremely careful about *ex*cluding unneeded CTEs - it's currently aimed
at being extremely careful to *in*clude CTEs that *are* needed.)

--
Tim Ward