Hello G. Deward,
We understand that this appears as a limitation for many scenarios. The reason it was developed this way is the risk of unwanted drop statements leading to loss of important information in the database.
We already have a feature request in our backlog about applying the model on the database as is, as an advanced option of the wizard. It will definitely be considered in our Q3 2012 planning.
Thank you for the feedback and do get back to us if you have any other observations about OpenAccess ORM and the possible improvements.
All the best,
the Telerik team
OpenAccess ORM Q2'12 Now Available! Get your hands on all the new stuff