Hello,

In our project we have existing entities that were generated from the database. If I add or remove a column in a database table, the related entity in the Designer needs to be updated. I've spent a lot of time adding RIA attributes and making adjustments to the entities in our model, and don't want to lose all my work, so I am hoping that you can tell me how to accomplish this task without losing my edits on the original entities.

I understand how to generate the update scripts so I can update the database from changes made to entities. But, more often, I make changes to the database and want to update entities... This is what I cannot figure out...

I know that I can completely regenerate the entities from the database, but then I lose all my configuration changes in the entities (i.e. RIA attributes, etc.).

Anyway, I hope that you can give me the procedure... It is probably very obvious, but I've missed it.

Thanks,

Mike

P.S. We recent did a two week comparison of LLBLGEN vs OpenAccess, and decide to use your product. It is much more stable, faster, and seems to work better with Oracle. Great work you guys!

Thank you for the feedback.

You can always Refresh the Catalog, and so your entities will be updated accordingly without affecting non-changed fields/entities.

In the Catalog Explorer, Right-Click on the "Relation Model Data" and select "Refresh Relation Model ..."

Also please check the properties inside the "Catalog Refresher" group, of the Project Properties.

Indeed, there are settings which auto-update your project, or leave the fields as-is (but unmapped) so you can map them later on or create new fields.

Thank you! Your recommendations worked perfectly!

ABOH wrote:

P.S. We recent did a two week comparison of LLBLGEN vs OpenAccess, and decide to use your product. It is much more stable, faster, and seems to work better with Oracle. Great work you guys!

Mike,

We evaluated OpenAccess as well and found it too unstable, we thought it would make sense seeing as we use Telerik components but it was just too buggy and the stored procedure support fell way short of what LLBLGen offers and the documentation was out of date or very poor, the support guys were helpful though.