>An Entity is a representation of data in memory. It can be a single table or multiple tables. What makes it easy is you just ask the data layer for the entity you need, without worrying about where that data is stored or how many tables are joined to get you that data.
>
>For example, if you want invoice #43, that's what you ask for. You don't worry about joining InvoiceHeader, InvoiceDetail, Customer, Parts, Shipping, etc, tables, nor do you care that those tables were joined to get the info.

Ok, this sound nice (and familiar to me) but who/where does what 'he should not care about' ?
(because that is almost all I care about! )

According to terminology I would suspect that this is happening somewhere in datalayer
or this is as well done at entity level ? (in som foundation classes of NET framework)

What are the possibilities there in terms of programming / modelling / datamunging.
For instance I want to control contingency scenarios. (Multiple users accesing the same records etc)

Pls don't tell me that this is blackboxed somewhere and customisable as easy as BIOS... {g}