ODBC, MAPI, Video for Windows, NetDDE, & RAS/RPC Under Win32s

Last reviewed: January 6, 1997
Article ID: Q147432

The information in this article applies to:

Microsoft Win32s version 1.30, 1.30a, 1.30c

The following interfaces are not completely supported under Win32s. Any exceptions are noted.

RAS API and RPC.
Video for Windows API (note that the MCI interface is supported).
MAPI interface (Also, a Win32s client can not thunk down to 16-bit MAPI in Windows 3.x. You will have to write a 16-bit client that calls the 16-bit MAPI APIs, and then have the Win32s client thunk to this 16-bit client). For more information on why a Win32s client (a 32-bit thunk DLL) cannot thunk to the 16-bit MAPI DLL, please refer to the following Knowledge Base article:
```
     ARTICLE ID: Q149710
     PRB: Why Thunking to 16-bit MAPI Will Fail Under Win32s
```
NetDDE interface.
ODBC (Win32s supports only ODBC version 2.0 and 2.1. Later versions of ODBC were not completely tested on Win32s).

KBCategory: kbinterop
KBSubcategory: w32s
Additional reference words: 1.30 1.30a 1.30c kbinf

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: January 6, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.