http://bugs.winehq.org/show_bug.cgi?id=29961
--- Comment #5 from Barry Bird birdfamily715@googlemail.com 2012-02-21 07:01:08 CST --- In response to a request for clearer instructions on running a test case I offer this: Here is a command script for Windows, assuming you have MDAC installed and .Net 2.0 and (I think) a .NET SDK:
SET PATH=%PATH%;%WINDIR%\Microsoft.NET\Framework\v2.0.50727;C:\Program Files\Microsoft.NET\SDK\v2.0\Bin REM Imports the ADO Type Library into .NET: tlbimp "C:\Program Files\Common Files\System\ado\msado15.dll" /namespace:ADODB /out: Interop.ADODB.dll REM Compiles the C# source files referencing the type library: csc /out:adonet1.exe /reference:Interop.ADODB.dll adonet1.cs csc /out:adonet2.exe /reference:Interop.ADODB.dll adonet2.cs
and compile odbc4.c in mingw: gcc -I/mingw/include -Wall -c odbc4.c gcc -L/mingw/lib ./odbc4.o -o odbc4.exe -lodbc32
Plainly, you can edit these source files to make further tests.
Copy Interop.ADODB.dll adonet1.exe adonet2.exe and odbc4.exe to the same directory under Wine and run this script:
cp test.mdb testrun.mdb # populates the database wine adonet2.exe testrun.mdb # shows what the database table contains: wine odbc4.exe testrun.mdb # runs the query program that fails under wine: wine adonet1.exe testrun.mdb