R
Rob Riggs
Guest
We currently unlock the branded drivers by dlopening them and calling SetLicenseInfo(). This works when using the branded driver manager with branded Data Direct drivers. However, we are also licensed to use the branded Data Direct driver manager with third-party drivers. The only way to allow the driver manager to load these third-party ODBC drivers is by setting the license information via the SQLSetConnectAttr() calls. That does not work for our use case. And without doing this, the driver manager attempts to load the default license file. Please provide a function, such as SetLicenseInfo(), which can be called on the driver manager itself to supply the license information. Ideally this call would be made once and the need to unlock individual drivers would no longer be necessary.
Continue reading...
Continue reading...