Telerik OpenAccess will generate the data access layer for your applications after just a few mouse clicks. All you have to do is to create the data model of your application and the tool will do the rest!
It's easy, quick, and powerful.
Telerik OpenAccess ORM takes over the mundane tasks of generating the data access code for your .NET application (C# or VB.NET), effectively relieving you from a significant portion of your relational data persistence tasks. The generated code has already been tested extensively by Telerik and conforms the latest object-oriented development standards. By doing the heavy lifting, OpenAccess ORM can save you between 20% and 85% of development and testing time.
Telerik's object-relational mapping tool has been designed to help, rather than to intervene. It uses just a few megs of memory on the client, it is extremely efficient when fetching data (even in large data-intensive applications), and comes with many tools and techniques to help you optimize the data access performance even further.
The Telerik ORM tool works equally well in all .NET platforms: ASP.NET, AJAX, MVC, Silverlight, WPF, Windows Forms, and Azure. It provides integration with WCF Ria Services, WCF Data Services, and more. It also integrates well with all Telerik developer tools and controls.
The powerful Visual Entity Designer of OpenAccess provides click-only model creation and drag & drop object-to-tables mapping. Based on your model, the tool instantly generates the data access code of your application. In case you feel that it can be improved, you can always update it manually, or use the available wizards and tools in Visual Studio to tweak it to your liking.
Telerik's object-relational mapper offers built-in support for more than 12 databases, including SQL Server, Oracle and MySQL. You can map classes to Views, Tables, and Stored Procedures. The latter is backed up by a Stored Procedure Editor which simplifies the setup and usage of stored procedures to just using your mouse. What is more, OpenAccess ORM allows you to seamlessly create database-independent code in case you decide to change the data store later on.
Comments