The information in this article applies to:
SUMMARY
Shared dynamic-link libraries (DLLs) in your system older than those
supplied with Microsoft Access version 1.0 or Microsoft Windows
version 3.1 can cause unexpected errors with Microsoft Access.
MORE INFORMATION
The shared DLLs used by Microsoft Access are:
(These DLLs are used by Windows applications other than Microsoft Access, as shown above. The DLLs for which no date is provided are the same for all applications.) Microsoft Access supplies the same DLL versions as Windows 3.1, and it requires these (or newer) versions for correct operation; older versions can cause errors. Microsoft Access and Windows copy shared DLLs into the WINDOWS\SYSTEM subdirectory, and that is where Microsoft Access first looks for them. If it does not find one or more of the shared DLLs, it looks in the directory where Microsoft Access is installed, and then in the current directory. Often, Microsoft Access finds outdated or incorrect DLLs because third-party software with old or foreign DLLs has been installed or reinstalled, overwriting the correct DLLs. Some third-party software packages copy DLLs into directories other than WINDOWS\SYSTEM, creating multiple copies and making the problem harder to track and resolve. Microsoft Access will not reload DLLs previously loaded by another software package; it will only load shared DLLs not already loaded. If the previously loaded DLLs are incorrect, they can cause problems with Microsoft Access. If the Microsoft Access Setup program fails to locate a shared DLL, or detects an older version of one, it issues an error message such as: -or-
Additional query words: WinIss
Keywords : kbenv |
Last Reviewed: March 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |