Thanks John,

I can see that could explain why i needed to change the file in the source runtime  before building the CAL

Still this will be a pita when going to new runtime versions - because this will be a subject of forgetness 

Having the PBODB.ini customized according to the client APP - the idea of having a general launcher is fading  away

If the Appeon guys changed the (execution) searchpath of pbodb.dll ( apppath , dllpath) this would be the right implementation 

I usuasally don't use ODBC - but had to use it for a new application - as the database i Postgresql

( therefore looking forward to pb2025 with .Net drivers )

Regards

Georgios

Hi, Georgios - 

I don't use ODBC, but I found some information in the Application Techniques publication, under the section heading "PowerBuilder ODBC interface files" that pertains to your situation:

    https://docs.appeon.com/pb2022/application_techniques/Database_connections.html#ODBC_database

-------------

Notes

The PBODB.ini file must be in a directory defined by the HKEY_CURRENT_USER\Software\sybase\PowerBuilder\22.0\InitPath registry setting or, in the absence of that key, in the same directory as the DLL file. In most cases, the target deployment machine will not have the registry setting and, therefore, the INI file should be in the same directory as the DLL.

-------------

I hope this helps explain the behavior you are experiencing.

Best regards, John