http://bugs.winehq.org/show_bug.cgi?id=32364
--- Comment #30 from Nikolay Sivov bunglehead@gmail.com 2012-12-29 15:16:07 CST --- (In reply to comment #28)
(In reply to comment #27)
So what I actually mean is that it would be interesting to go through same steps as we did (install jet40 with winetricks - it will install provider with exact name your application wants) and flip oledb32 to builtin before launching application. Please try that with current wine from git and in any case attach new log for +oledb,+tid.
OK... JET40 is already installed but I tried a re-install anyway as follows: winetricks jet40 Executing w_do_call jet40 JET40 already installed, skipping
It's better to start with clean wineprefix. Once you have installed it with jet40 you should have Microsoft.Jet.OLEDB.4.0 provider in registry, and if it's present builtin code should be able to use it. I have no explanation why native works for such provider name even if it's not registered - could be that application request error info we don't support and adjust provider name accordingly, or could be something entirely different.
So to try now:
- clean wineprefix - winetricks jet40 - oledb32 to builtin - logs