is actually a stub for libdb48d.DLL). To check this
setting in Visual C++, choose the <spanclass="emphasis"><em>Project/Settings</em></span> menu
item and select <spanclass="emphasis"><em>Code Generation</em></span> under the tab marked
<spanclass="emphasis"><em>C/C++</em></span>; and see the box marked <spanclass="emphasis"><em>Use runtime
library</em></span>. This should be set to <spanclass="emphasis"><em>Debug Multithreaded DLL</em></span>.
If your application is linked against the static library,
build_windows\Debug\libdb48sd.lib; then, you will want
to set <spanclass="emphasis"><em>Use runtime library</em></span> to <spanclass="emphasis"><em>Debug Multithreaded</em></span>.</p>
<p>Setting this option incorrectly can cause multiple versions of the
standard libraries to be linked into your application (one on behalf
of your application, and one on behalf of the Berkeley DB library). That
violates assumptions made by these libraries, and traps can result.</p>
<p>
Also, using different Visual Studio compilers in the application and
libraries can lead to a crash. So rebuild the application
with the same Visual C++ version as that of the library.
</p>
</li>
<li>
<spanclass="bold">
<strong>Why are the build options for DB_DLL marked as "Use MFC in a Shared DLL"?
Does Berkeley DB use MFC?</strong>
</span>
<p>Berkeley DB does not use MFC at all. It does however, call malloc and free
and other facilities provided by the Microsoft C runtime library. We
found in our work that many applications and libraries are built
assuming MFC, and specifying this for Berkeley DB solves various
interoperation issues, and guarantees that the right runtime libraries
are selected. Note that because we do not use MFC facilities, the MFC
library DLL is not marked as a dependency for libdb.dll, but the
appropriate Microsoft C runtime is.</p>
</li>
<li>
<spanclass="bold">
<strong>How can I build Berkeley DB for <aclass="ulink"href="http://www.mingw.org"target="_top">MinGW</a>?</strong>
</span>
<p>Follow the instructions in <aclass="xref"href="build_unix.html#build_unix_intro"title="Building for UNIX/POSIX">Building for UNIX/POSIX</a>, and specify the --enable-mingw option to the
configuration script. This configuration option currently only builds
static versions of the library, it does not yet build a DLL version of
the library, and file sizes are limited to 2GB (2^32 bytes.)</p>
</li>
<li>
<spanclass="bold">
<strong>How can I build a Berkeley DB for Windows 98/ME?</strong>
</span>
<p>
Windows 98/ME is no longer supported by Berkeley DB. The following is
therefore only of interest to historical users of Berkeley DB.
</p>
<p>
By default on Windows, Berkeley DB supports internationalized
filenames by treating all directory paths and filenames passed to
Berkeley DB methods as UTF-8 encoded strings. All paths are
internally converted to wide character strings and passed to the
wide character variants of Windows system calls.
</p>
<p>
This allows applications to create and open databases with names
that cannot be represented with ASCII names while maintaining
compatibility with applications that work purely with ASCII paths.
</p>
<p>
Windows 98 and ME do not support Unicode paths directly. To build for
