LINQ-Join tables on nullable columns?

Dim query = From charge In Services.dsERP. ERP_Charge _ Join rma In Services.dsRMA. RMA _ On charge.

IdCharge Equals rma. FiCharge _ Where rma. FiCharge Nothing AndAlso rma.

IMEI = imei Select charge. IdCharge If that doesn't work, you could try something like this: Dim query = From charge In Services.dsERP. ERP_Charge _ Join rma In (From rma in Services.dsRMA.

RMA _ Where rma. FiCharge IsNot Nothing Select rma) On charge. IdCharge Equals rma.

FiCharge _ Where rma. IMEI = imei Select charge.idCharge.

Thank you, the second query works after replacing rma. FiCharge Nothing with Not rma. IsfiChargeNull :) – Tim Schmelter Apr 18 at 7:49.

While you can use LINQ to Datasets to solve this issue, you might find better performance using the predefined DataRelations instead of ad-hoc joins. See msdn.microsoft.com/en-us/library/dbwcse3... for information about data relations. If you do use LINQ to Datasets, you might want to check out our free bonus chapter 14 on them at manning.com/marguerie/.

I don't think that DataRelations are much faster than LINQ-Joins since their also using hash algorithms to link the tables but LINQ is much more flexible. – Tim Schmelter Oct 19 at 18:46 I think those optimizations with the hash algorithm apply only if you are using . Net 4+.

If using 3.5, the Dataset DataRelation is the better option. – Jim Wooley Oct 20 at 16:39.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.