tag:blogger.com,1999:blog-5110857384844141930.post6565386439586697787..comments2023-09-25T12:37:04.271+04:00Comments on Nitin's Tech Blog: LINQ to Entity JoinsNitin Reddy Katkamhttp://www.blogger.com/profile/09612217398194148324noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5110857384844141930.post-12129260214696058742011-11-25T18:41:53.538+04:002011-11-25T18:41:53.538+04:00I was hoping to get your help on this, I am gettin...I was hoping to get your help on this, I am getting the same error, but am not sure how to do it...and I have tried many ways... the <br />AGREEMENT_PACK table is a reference table between the other 2...<br /><br />ObjectQuery c2a = db.AGREEMENT;<br />IQueryable AGREEMENT_IDS =<br />from com2d in c2a<br />from com2c in com2d.AGREEMENT_PACK<br />from com2b in com2c.PACK<br />from com2a in com2b.ADMINISTRATION where com2a.DESC1.Contains(keyWord) || com2a.DESC_EN.Contains(keyWord)<br />select com2d.AGREEMENT_ID;<br /><br />Here are the relation keys<br /><br />AGREEMENT_PACK.PACHID = PACK.ID <- foreign key<br />AGREEMENT_PACK.AGREEMENTID = AGREEMENT.ID <- foreign key<br />PACK.AdminId = ADMINISTRATION.ID <- foreign keyAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5110857384844141930.post-56969582254118076512009-04-03T07:46:00.000+04:002009-04-03T07:46:00.000+04:00@PancreatistI'm glad I could help. BTW, you ought ...@Pancreatist<BR/><BR/>I'm glad I could help. BTW, you ought to try out LLBLGen. It's an ORM that acts as a Linq provider and gets around many of the limitations that Linq-to-SQL and Linq-to-Entities impose.Nitin Reddy Katkamhttps://www.blogger.com/profile/09612217398194148324noreply@blogger.comtag:blogger.com,1999:blog-5110857384844141930.post-2157611870529628972009-04-03T02:36:00.000+04:002009-04-03T02:36:00.000+04:00Thank you, this worked for me. I was wondering wha...Thank you, this worked for me. I was wondering what the heck was going on... :PAnonymousnoreply@blogger.com