Hi,
The MS Office 95/97 setup program fails when using the built-in odbccp32.dll. A native version of this dll is on the installation media. Since 2005-07-08, Wine doesn't use this file because of this patch: http://cvs.winehq.org/patch.py?id=18748
I think that we have three options: - Change Wine's default configuration and make it use the native odbccp32.dll - Add a remark in the application DB to Office 95/97, Access 95/97, Excel 95/97 (also Word 95/97, Powerpoint 95/97?) that users should use winecfg to change "odbccp32" to "native, builtin" - Implement the needed functions in odbccp32.dll
See also bug 3268: http://bugs.winehq.org/show_bug.cgi?id=3268
PS: odbccp32.dll is missing on Wine's status page.
Regards Michael
Michael Kaufmann wrote:
The MS Office 95/97 setup program fails when using the built-in odbccp32.dll. A native version of this dll is on the installation media. Since 2005-07-08, Wine doesn't use this file because of this patch: http://cvs.winehq.org/patch.py?id=18748
Does Office 95/97 ship a version of odbccp32.dll in C:\windows\system, or in some other directory?
- Implement the needed functions in odbccp32.dll
Ofcourse implementing the necessary functions would be the best solution, but until somebody does that I guess putting a note about dll overrides in the appdb would be OK.
If we simply set odbccp32=n in the default user.reg nobdoy is going to fix it.
Mike
The MS Office 95/97 setup program fails when using the built-in odbccp32.dll. A native version of this dll is on the installation media. Since 2005-07-08, Wine doesn't use this file because of this patch: http://cvs.winehq.org/patch.py?id=18748
Does Office 95/97 ship a version of odbccp32.dll in C:\windows\system, or in some other directory?
Office 95 does not. Office 97 puts it in C:\Windows\System32, together with a lot of other ODBC dlls, for example odbccp32.cpl and odbcad32.exe (a configuration tool for ODBC data sources).
- Implement the needed functions in odbccp32.dll
Ofcourse implementing the necessary functions would be the best solution, but until somebody does that I guess putting a note about dll overrides in the appdb would be OK.
Right now only Office 2003 is in the application DB. "MS Office Setup" is also listed as an application. We probably have to add entries to every stand-alone application too (Access, Excel). Anybody wants to do this?
Regards Michael
-
Michael Kaufmann -
Mike McCormack