hiya Walaa,
Thanks for the reply.
I need the functionality for databinding.I'm already aware of being able to bind to aliases in a typedList.That isn't the issue.
So, as you say..
From the above I understand that you want to have something like a pivoting behaviour.
Where you get values from different rows (from the tblSkill) to be displayed in one row (cell).
Correct, however, the typedListOne (tblDog) already binds to the grid.
What I need to do is ADD values from different rows (from the tblSkill) to be displayed in one row (cell)
Therefore, my grid will be as follows
column1 column2 etc
tListOne field tblSkillFields etc
So, I need to keep typedListONE and add the fields from typedListTWO (tblSkill)
TypedListONE is quite complex.
You may a property to the main entity (tblPersonSkill or tblDog), and call it LongDesc for instance.
Then in the Get of this property you loop on the related Collection to get required field of each entity in this collection and append it to the output of the LongDesc property.
Then you should fetch the collection instead of the TypedList.
As I mentioned, typedListONE is quite complex.Why can't I just add a column to it that contains these values?
If I have to discard typedListONE, then that means that I have to somehow re-create it as a collection??
..this seems like duplicated effort.
Obviously, all of this is new to me.Why do I have re-create typedListONE as a a collection?
Thanks,
yogi