odbc progress openedge wire protocol driver

Sb. Sb.AppendLine('SELECT EmpID as 'EmployeeID',') Using (OdbcCommand command = new OdbcCommand())Ĭommand.CommandText = GetEmployeeDataQuery() Ĭ('empID', OdbcType.NVarChar) Public EmployeeDataModel GetById(string id)

Public EmployeeRepository(string connString) The connection string to connect to the DB: connectionString='PROVIDER= MSDASQL DRIVER= For the latest support information, visit the Progress DataDirect Supported Configurations page.

I cannot change the DB technology, we are connecting to an Progress DB. The DataDirect Connect for ODBC and DataDirect Connect64 for ODBC PostgreSQL Wire Protocol driver (the PostgreSQL Wire Protocol driver) each support PostgreSQL database servers.

Some background and restrictions to my scenario: After making all modifications, save the odbc.ini file and close the text editor. This causes problems with the scenario where I am trying to use Dapper. In the ODBC section at the beginning of the file, add a new datasourcenameinstalled-driver pair containing the new data source name and the appropriate installed driver name. The problem with that question's answer and with the example given in the documented Git examples is that a true ODBC object is not being used, but rather an OleDbConnection object. The only thing that was going wrong was the query syntax from the Github example was not valid using the ProgressDB OpenEdge driver. Passing query parameters in Dapper using OleDbĮDIT: The troubleshooting below is somewhat misleading. Here is the related question I have already read: Please read the comments of the answer for a more complete understanding of what the problem is/wasįirst, I read through a lot of the other SO questions related to this and still can't get this to work with a basic setup.

Odbc progress openedge wire protocol driver