Install old drivername with link to new driver dll

[BFuerchau]

We have many products, where the drivername is hardcoded with "Driver={Firebird/InterBase(r) driver}", so wie don't have a DSN.
Can you please additional register the old drivername with a link to the new dll?
The reason is, that at one customer can the old ODBC-driver not install because of alleged security vulnerability.

After registry change with regfile, my appication works.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBCINST.INI\Firebird/InterBase(r) driver]
"UsageCount"=dword:00000001
"Driver"="C:\WINDOWS\system32\FirebirdODBC.dll"
"Setup"="C:\WINDOWS\system32\FirebirdODBC.dll"
"FileExtns"=".fdb,.gdb"
"APILevel"="1"
"ConnectFunctions"="YYY"
"FileUsage"="0"
"DriverODBCVer"="03.51"
"SQLLevel"="1"

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\ODBC\ODBCINST.INI\ODBC Drivers]
"Firebird/InterBase(r) driver"="Installed"

The existing DSN's works also but can not be configured with the new driver.

[mrotteveel]

I've reopened this, as I think it may still be good to do (maybe as an option in the installer?)

[mrotteveel]

@BFuerchau With your current registry changes, you've only applied it for 32-bit applications

[BFuerchau]

Thats right, because for 64 Bit i use .Net FirebirdClient.
I have made two .reg-Files. But i have changed all 32-bit modules, from a central Object, and look now first to the new driver name and second to the old through the registry entries.
But not alle Customers want the new version, but need perhaps the registry entry.

What i not understand is, that the setup entry name the new driver dll, but old DNS-Entries can't be edited.
Perhaps you can try to find, why this isn't possible. I think, with the registry old entries could in case of edit renewed with the new driver. The problem here is, that the driver is in machine config, but we may have many user DSN's.
Perhaps with a simple, user defined updater button in the Setup-Dialog?
Or you scan the current user-DSN's, if you find old firebird driver, you show a Update-Messagebox.
The Setup is called in User environment, so you have access to all DSN's from the old driver.
If i setup with the new driver, i can than update all old DSN's.

For us, we can write our own powershell-script to do this.

[mrotteveel]

I think the point is that you can install them side-by-side. Right, @irodushka ?

[BFuerchau]

Yes, it works but makes no sense.
The main reason is a message from a customer, that the 2.5 Driver has a security risk and should not used any more.
So many thanks, that you renew the old driver.
Our own software, old 32-Bit-VB6 just working also on Server 2025, works without DSN, as dicussed in the other thread.
But other software like SQL-Server or Power-BI must access with DSN's.
At the moment, the current DSN can not be configured and a driver can't be changed per setup.
So for us, i can solve this with the update with in the ODBC.INI-Path.
I have just looked in one config and see, that in Driver the DLL is named and not the Drivername.
So these entry has to be changed. Also in the Subbtree "ODBC Data Sources" must be the Drivername changed.
If i change this manually, the confiuration can be changed.