http://bugs.winehq.org/show_bug.cgi?id=3967
------- Additional Comments From tuharsky@misbb.sk 2005-01-12 01:35 ------- Please, note that:
1, Until now, there isn't native odbc backend in wine, although requested more than 3 years ago.
2, There is a way to enable it, using native ODBC dll's (from myODBC 2.5 installation), that even WORKED WELL until 200505 version of Wine (see 3966).
3, This is the only way to run free Oracle client with apps under wine, because Oracle dosen't support ODBC driver for Linux.
4, Wine indeed IS about making native DLL's work too, especially if they aren't implemented by wine. If it wasn't, hardly could any slightly more complex app work. Nice example: it is even adviced to use common controls native DLLs sometimes. And they are even implemented! So much more should Wine care about handling those DLL's that aren't implemented either. Especially those that are essential to run apps.
"Wine is an Open Source implementation of the Windows API". Logically, if the API is implemented correctly, the DLL's should work too, don't they?
5, Since yesterday, under my closer inspections, this bug seems to be not about odbcad32.exe itself, but rather about the very ODBC libraries under wine. Even if it was just about odbcad32.exe, what's wrong about it if it was necessarry to run app under wine? The DB sources must be defined somehow, and odbcad32.exe is good way to do it.
Eventually, it is stil all about compatibility with Window$...
If You be so kind and wish to help us with problem 3966 that puts our Linux installations under danger, then odbcad32.exe is good way to test the native ODBC libraries behaviour. If they worked well with odbcad32.exe, then they will surely work with our very essential app.
If my expectations are right, than this issue could be marked as duplicate of 3966. What do You suggest?
-
Wine Bugs