once more I´ve forgotten something...namely the calling of that expression:
Expression> whereLogonName = LinqExtender.DynamicLinq.BuildOrTree(LogonName, Users_Users => Users_Users.LogonName);
Expression> whereLogonPW = LinqExtender.DynamicLinq.BuildAndTree(siteparam, Users_Users => Users_Users.LogonPW);
Users_UserAccount medProOrignal = ce.Users_UserAccount.Where(whereLogonName).Where(whereLogonPW ).First();
but I found out, that there´s a 'priority-problem', when using .First(); but that´s so obvious... consider the following: two users: user a: UID:1 logonname: gargamel PW: a user b: UID:2 logonname: gargamel PW: b actually I've overseen the fact that I was using .First() .First() will simply take UID1 becoz it´s the first one found... now I've tried it with .Single() and it returns the desired user... but what left me dumb is the fact, that I can´t see the way this query get´s prioritized in terms of params... :confused: actually, I hope my question is considerably clear and that I forgot nothing... :doh: :doh: :doh: [eeedit] I "profiled" it in SQLM MGMT Profiler but i´m veeery weak in SQL... no clue at all.. :thumbsdown:
