this looks like to be an issue. There seems to be an explicit comparison with a bool value of true/false at the end, and this causes a push to the server (1=0 expression), generating invalid SQL.
As a workaround, you could eliminate == false as well as == true from the generated expression via LINQ expression manipulation, but this might a bit of effort for you.
I've filed a bug entry for this issue, but I cannot promise any fix date for the moment.
Thanks for reporting this issue back with us.
OpenAccess ORM is now Telerik Data Access
. For more information on the new names, please, check out the Telerik Product Map