FIX: ODBC SDK May Overwrite Latest Version of Msvcrt20.dll

The information in this article applies to:

• Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0

SYMPTOMS

If Visual Basic 4.0 is already installed before you install the ODBC SDK, Visual Basic fails to start and gives this error message:

   The procedure entry point _adjust_fdiv could not be located in
   the dynamic link library Msvcrt20.dll

CAUSE

The ODBC SDK versions 2.10a and earlier fail to check versions on the file Msvcrt20.dll. It will blindly copy over any previously existing copy of the .dll file. In this case, the ODBC SDK is copying Msvcrt20.dll version 2.00.000 over the Msvcrt20.dll version 2.10.000 that comes with Visual Basic 4.0. Because compiled applications use Msvcrt20.dll (it is a dependency of Vb40032.dll), this problem may also affect compiled applications on computers that do not have the Visual Basic 4.0 32-bit development environment installed.

The ODBC SDK also overwrites the Mfc300.dll file, but this file isn't included with Visual Basic.

RESOLUTION

Extract the newer version of the Msvcrt20.dll from your original Visual Basic floppy disks or compact disc, and copy it over the old version installed by the ODBC SDK. The extract.exe program (a new version of which comes with Visual Basic) can be run using the following line to extract the file to the directory you specify (replace the path after the '/l' switch):

   extract /e /l c:\temp vb4-1.cab msvcrt20.dll

STATUS

Microsoft has confirmed this to be a bug in versions of the ODBC SDK earlier than 2.10b. This problem was correct in version 2.10b and later.