Telerik OpenAccess Classic

Telerik OpenAccess ORM Send comments on this topic.
Using the NTDS driver
Programmer's Guide > OpenAccess ORM Classic (Old API) > OpenAccess Tasks > Connections and Data Store Management > Using the NTDS driver

Glossary Item Box

This documentation article is a legacy resource describing the functionality of the deprecated OpenAccess Classic only. The contemporary documentation of Telerik OpenAccess ORM is available here.

Telerik OpenAccess ORM uses a low-level driver for the actual communication with the database system.

Name Description

– supports SQL Server 2000 or later, MySQL
5.0, Advanatage Database Server 8.1,
SQLExpress, SQL Anywhere Server, SQL Azure, Microsoft SQL CE and
– supports Oracle 9i and higher

ODP – .driver using ODP.NET (Oracle Data
– supports Oracle 9i and higher

Explicitly changing the driver:

In order to be able to use SQL 2000 you will need to use the genericADO2 driver that comes together with Telerik OpenAccess ORM. To do this you will simply need to alter the backend configuration node located in the app.config. The only thing that needs to be added is the driver attribute. Here is an example of how the backend sections should look like:

app.config Copy Code
backendconfiguration id="mssqlConfiguration" backend="mssql" driver="genericADO2">

This can also be done from the Backend configuration setting wizard.

  1. Open the Telerik menu and point to OpenAccess.
  2. Point to Configuration.
  3. Choose Backend Configuration Settings.
  4. The setting can be changed from the Database Driver combo box.

Once a connection is established, the user must be able to log in. This can be achieved by either creating a user within the SQL server (limiting the login-scope to the database server) or more easily by allowing mixed mode (Windows and SQL Server) logins.