This question is locked. New answers and comments are not allowed.
Hi,
I start using OpenAccess as it was invited by Vanatec long before it was sold to Telerik.
The absolute premium feature is (was?) the ability to start with an object model and automatically create the database structure. You only have to use one tool, and dont have to deal with DDL, SQL or wathever. Even when you have to change something, the changes were reflected in a script and automatically applied to your development db, later on used to upgrade the customers installations.
Now I start reading about the new Data Designer and Domain Model and ...
As far as I can see, I have to handcraft my database and than use 'New OpenAccess' to get an object model.
Can me somebody tell why this is an advance? I also can use Microsofts Entity Framework, which I get without additional costs as part of VS2010, so why using 'New OpenAccess' ?
Or were there some plans to support the marvelous 'objects first' approach some day with the new stuff, which makes 'Classical OpenAccess' so outstanding of the crowd of many dozends of mappers I evaluated more or less?
Hope you don't kill the product in the future.
Or do I just miss some importent parts during reading the documentation ? (Hope so!!)
Thanks a lot.
With best regards
DI Gerhard Kreuzer
I start using OpenAccess as it was invited by Vanatec long before it was sold to Telerik.
The absolute premium feature is (was?) the ability to start with an object model and automatically create the database structure. You only have to use one tool, and dont have to deal with DDL, SQL or wathever. Even when you have to change something, the changes were reflected in a script and automatically applied to your development db, later on used to upgrade the customers installations.
Now I start reading about the new Data Designer and Domain Model and ...
As far as I can see, I have to handcraft my database and than use 'New OpenAccess' to get an object model.
Can me somebody tell why this is an advance? I also can use Microsofts Entity Framework, which I get without additional costs as part of VS2010, so why using 'New OpenAccess' ?
Or were there some plans to support the marvelous 'objects first' approach some day with the new stuff, which makes 'Classical OpenAccess' so outstanding of the crowd of many dozends of mappers I evaluated more or less?
Hope you don't kill the product in the future.
Or do I just miss some importent parts during reading the documentation ? (Hope so!!)
Thanks a lot.
With best regards
DI Gerhard Kreuzer