as I understand it when using WPF with the MVVM pattern, on the Model side of things, you can have your classes and entity data classes(which act as a type of database access).
I have run my eye over a few tutorials that have used a 'ADO.NET Entity Data Model' in VS2010 to produce the classes for the entities. Table and column definitions are hard-coded.
My question is, in part of my application users will be able create their own tables, in this case can the entity model still work? Up until now it seems a little inflexible. My system tables will very rarely change, however user tables will. How and can it handle being dynamic?