Microsoft Access 2.0 - Error calling 32 bit ODBC driver

[LegacyFreak]

Hello,
I tried to get Access 2.0 to work with 32 bit ODBC. These steps I have done so far.

1. Copied the files ds16gt.dll, ds32gt.dll, odbc16gt.dll and odbc32gt.dll from an existing Windows XP installation where Access 2.0 successfully runs with 32 bit ODBC into the Windows system directory in OTVDM.
2. Created two 32 bit ODBC datasources for Oracle and Access with the 32 bit ODBC Administrator
3. Installed Access 2.0 and ODBC 2.0 (16 bit) in OTVDM.
4. Copied the entries, which are related to my datasources, from ODBC.INI in Windows 10 into my ODBC.INI in OTVDM.

Now I can see the 32 bit data sources within the 16 bit ODBC Driver Manager in OTVDM.
When I select one of my 32 bit datasources in Access 2.0 to create a linked table, I get the follow error message. This is the same for the Oracle and the Access datasource (see screenshot and trace).

trace.zip

[cracyc]

Google translate gives me "Invalid window handle". Since winevdm doesn't share hwnds with win32 the way ntvdm does, they have to be translated going in and out. Usually CallProc32W is used for calling from win16 to win32 and there's some window handle translation in there already, this will probably need adding.

SQLDriverConnect looks to be the problem here. https://docs.microsoft.com/en-us/sql/odbc/reference/syntax/sqldriverconnect-function?view=sql-server-ver15 A look though the wine source doesn't show any other SQLHWND users. But it looks like it tried to do the translation itself:

1f64:Call KERNEL.517: CALLPROC32W(0000000f,00000540,7528109b,...) ret=2f7f:1962 ds=2f87
1f64:fixme:thunk:K32WOWHandle32 513: conversion of full window handles not supported yet
1f64:Ret  KERNEL.517: CALLPROC32W() retval=0000ffff ret=2f7f:1962 ds=2f87

[LegacyFreak]

Hello,
problem solved. Thanks for patch.