Andrus,

>Ideablade application can ask the Ideablade PersistenceManager to tell at run-time what data columns it founds in the live data source.
>
>Suppose the Ideblade appl connects to a database containing an Employee table. The application discovers an integer column called “MySpecialNumber”.
>
>The Employee class doesn’t have a MySpecialNumber property.
>
>The application can read and set Employee instance’s MySpecialNumber value using the indexing method. The PersistenceManager will update this data column in the data source when it saves the employee entity.

In reality, MM .NET can also work in a dynamic, untyped fashion. Ultimately, behind the scenes an entity object is a wrapper around untyped data (as is the .NET Typed DataSet). Even though you have specific properties on the entity at design time, the underlying DataTable can have additional columns which can be accessed at run time.

Best Regards,