Solved

Connect Progress database via ODBC

  • 5 October 2023
  • 5 replies
  • 173 views

Userlevel 2
Badge +2

I am connecting to an Openedge Progress database via ODBC drivers. After finding out the password needs to be set in the registry, I am able to connect to the source (test connection from the Data Source properties is succesful).

My sync task however fails because the datasource is not querying the correct metadata tables. In Progress, metadata for tables, columns and views is stored in the tables SYSTABLES, SYSVIEWS and SYSCOLUMNS. In the advanced settings of the datasource I am able to point out the correct column names, but not the correct tables (see screenshot below).

Does anyone know how to point the datasource to the correct metadata tables?

 

 

icon

Best answer by Thomas Lind 5 October 2023, 10:21

View original

5 replies

Userlevel 6
Badge +5

Hi @wouter.goslinga 

If you are using a ODBC data source, no matter what the actual ODBC provider you made in there it will be the same setup in that menu.

So it needs to look like this.

So it is the default look, only you remove the a from the schema and view schema name so it is TABLE_SCHEM instead of TABLE_SCHEMA.

I have a guide about the old way it was done here

https://legacysupport.timextender.com/hc/en-us/articles/4410466782621-Create-a-ODBC-data-source-in-a-ODX-or-with-a-Any-Source-ADO-Net-provider-in-a-Business-Unit

You can see specifically what I mean there.

Userlevel 2
Badge +2

Bit strange, but it did solve the problem :). Thanks!

Userlevel 6
Badge +5

If you used a Openedge Progress provider that existed as a specific data source, then what you did would be correct, but for all ODBC data sources those settings gets put behind another level.

For example, I had one for MySQL I used in the Legacy program where this was the case.

https://legacysupport.timextender.com/hc/en-us/articles/115005932243-Connect-to-MySQL-using-ADO-Net

This would be the same for progress if you had a ADO.Net data source.

Userlevel 2
Badge +2

@Thomas Lind so the way it works is that every ODBC driver has a built-in mapping from some general metadata ‘table’ names to the vendor-specific metadata tables that are actually in the database?

Userlevel 6
Badge +5

Yeah, something like that. I am not entirely sure how it works, but it is how it appears.

Reply