It is true that at the moment OpenAccess cannot handle more than one association based on the same foreign key member/column.
However, I think there is a good solution for your case which avoids this limitation. As the three views share the same id column, this means that the associations between the three views are 1:1 and one object always has the other two on the other side, there is no case of a null reference. Having this in mind, it should not make a difference if you define the associations the other way around, where SecurityCashFlow
have the foreign keys and Security
holds the primary key. You would get the same SecurityCashFlow and SecurityCurrent references in the Security class.
So please just try dragging the associations in the opposite direction and let us know if you face further difficulties.
the Telerik team
Follow @OpenAccessORM Twitter channel to be the first one to get the latest updates on new releases, tips and tricks and sneak peeks at our product labs!