> Well, depending on how SQLite was linked, it may turn out to depend on a version of C runtime that's not guaranteed by Windows to be present on a given system. The Windows dependency model is "take it with you", including a C runtime, one of many available versions. This is true, if one wants it to be true. It has been possible, however, since the begining of Windows NT (when it was called OS/2 New Technology) and even before, to generate executables that use what is known in patented IBM terminology as "the subsystem runtime" rather than a user conceived runtime. I always use the subsystem runtime because it is stable. And while Microsoft did remove the system trampoline for a few versions of OS/2 New Technology, they have now put it back, by default, on every system. Other people may choose to chase a proprietary user mode runtime that is subject to the whims of whomever created it (such as the various MSVC runtimes). That means that you can either deliberately choose to have problems, or deliberately choose to not have problems. Microsoft generally prefers the former (using proprietary runtimes from the "runtime of the month club") thus causing those using such ill-conceived "runtime of the month" to believe that there may be compatibility issues from one version of OS/2 New Technology to the next, where there is none. There is simply a change in the "runtime of the month" and the issues are by design.