The information in this article applies to:
SYMPTOMS16-bit applications may use the 32-bit ODBC data source name (DSN) even though use of the 16-bit ODBC is intended. The symptoms may vary, but unpredictable results can occur like using the unintended driver or the DSN. CAUSEThis behavior occurs because the 16-bit Driver Manager uses the Odbc.ini file for DSNs and the order in which the DSNs are present in the .ini file may determine the one that is actually used. This only occurs if duplicate DSNs exist in both the 16-bit and 32-bit environments. This will only impact 16-bit applications, since the 32-bit ODBC does not use the 16-bit Odbc.ini file. RESOLUTIONMake sure that the names in the 16-bit ODBC environment and the 32-bit ODBC environment are unique. Rename any duplicate DSNs and modify your applications to use the updated names. STATUSThis behavior is by design. Additional query words:
Keywords : kbODBC kbGrpMDAC kbGrpODBC |
Last Reviewed: October 27, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |