Why do I get a compilation error on Windows when I create a project using MFC or anything that includes oledb.h?
Berkeley DB’s header file db.h and Microsoft’s header file oledb.h both define the symbol DBTYPE. Unfortunately, changing either use of this symbol would break existing code. The first and simplest solution to this problem is to organize your source code so that only one of these two header files is needed in any of your sources. In other words, separate the uses of Berkeley DB and the uses of Microsoft’s OLE DB library so that they are not mixed in your code. Then, just choose either db.h or oledb.h, but do not mix them in one source file. If that is not possible, and you have to mix both headers, wrap one of the #include lines as follows. Find the line where oledb.h is included in your source code. This may be in the automatically-generated stdafx.h include file. Decide whether that header file is really needed.
Related Questions
- Why do I get an error message when I try to create a project in the BeadStudio 2 Gene Expression Module with both 6x2 and 8x1 BeadChips?
- Why do I get a compilation error on Windows when I create a project using MFC or anything that includes oledb.h?
- Why I get "PennCNV compilation error: Can locate loadable object" in Windows?
