This problem was caused by incorrect code generation for many-to-many associations. We have fixed it, and the fix is available in the latest 2.50.22 Beta build of LinqConnect. The new build can be downloaded from http://www.devart.com/linqconnect/download.html
(the trial version) or from Registered Users' Area (provided that you have an active subscription):http://secure.devart.com/