ADO.NET Connection Editor

The ADO.NET Connection Editor enables you to define and manage connection configurations used by the OpenESQL Managed Runtime when connecting a COBOL program to an ADO.NET or an ODBC data provider.

Connection information is stored in a standard .NET Framework repository, machine.config, which enables mixed language applications to share connection strings. The repository is accessible to all users of the machine on which it is installed.

The OpenESQL Managed Runtime supports any ADO.NET provider that supports the DbProviderFactory API.

  • We recommend that you use ADO.NET data providers when possible; however, the ADO.NET connection editor catalogs ODBC connections that you can use if necessary. This does not apply to COBOL Server.
  • When you run the ADO.NET Connection Editor under operating systems that have User Access Control enabled, you must run it as an administrator if you are adding, deleting, or updating connections for System type connections. However, when updating User or Azure type connections, you do not need this elevated authority. See the To start the ADO.NET Connection Editor as an administrator and To start the ADO.NET Connection Editor as a user topics for more information.
  • When you specify the Azure connection type, the Framework and Availability settings are disabled. This is because Azure SQL Database connections are stored in a single configuration file that does not contain provider framework or bitness information.
  • For Azure SQL Database connections, ignore the version information specified on the .NET Data Providers page of the Add an ADO.NET Connection wizard.
  • The ADO.NET Connection Editor works in combinations of 32- or 64-bit and framework 2.0, 3.0, 3.5 or framework 4.0, 4.5, 4.6, 4.7 and 4.8. Whichever mode you work in, you must have the 32-bit framework 4.0, 4.5, 4.6, 4.7, or 4.8 version of the provider that you want to work with your connection.