BUG: Debug DAO SDK Components Cause Assertion (192777)
The information in this article applies to:
- Microsoft Visual Studio, Enterprise Edition 6.0
- Microsoft Visual C++, 32-bit Professional Edition 6.0
- Microsoft Visual Basic Enterprise Edition for Windows 6.0
This article was previously published under Q192777 SYMPTOMS
Visual Studio version 6.0 comes with the DAO Software Development Kit
(SDK). If you try to build and run any of the samples in the
\DAOSDK\SAMPLES directory (such as DAOREAD or EMPLOYEE) on a computer with
Visual C++ version 6.0 and the DAO SDK from the DAOSDK directory on CD
number 3 (or from CD number 1 of the Visual C++ CD) installed, you get an
assertion failure and the following error message box appears:
Debug Assertion Failed
Program: C:\DAOSDK\SAMPLES\DAOREAD\DEBUG\DAOREAD.EXE
File: objcore.cpp
Line: 174
You may also see the following error message in your DAO SDK application:
Debug Assertion Failed
Program: C:\DAOSDK\SAMPLES\DAOREAD\DEBUG\DAOREAD.EXE
File: doctempl.cpp
Line: 30
CAUSE
You need to rebuild the debug versions of the DAO SDK DLLs for Visual C++
6.0 applications.
RESOLUTION
You need to rebuild DDAO35D.DLL (for non-Unicode builds) and DDAO35UD.dll
(for Unicode builds). To rebuild the dbDAO libraries, you need to use the
DBDAO.mak file in the \DAOSDK\SRC folder. Following is the command line to
rebuild DDAO35D.dll:
nmake /f dbdao.mak CFG="ddao - Win32 Debug"
Following is the command line to rebuild DDAO35UD.dll (this is only
necessary if you are building a Unicode release of your application and
have the MFC Unicode libraries installed):
nmake /f dbdao.mak CFG="ddao - Win32 Debug Unicode"
Use the new .lib and .dll files that are generated in the DEBUG or DEBUGU
folders.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article.
Modification Type: | Major | Last Reviewed: | 11/18/2003 |
---|
Keywords: | kbbug KB192777 |
---|
|