The information in this article applies to:
SUMMARY
CRecordset::SetFieldNull() causes an assert or an access violation if
called for a parameter. Even if no assert or access violation occurs, the
parameter may not be set to Null.
If SetFieldNull() is called after the recordset is open, then a call to
CRecordset::Requery() may assert in DBCORE.CPP at line 4055 or line 4062:
If SetFieldNull() is called after the recordset is closed and before it is
reopened, you will see an access violation in DBCORE.CPP at line 4057:
or at line 4064:
NOTE: Visual C++ 5.0 has a new function called SetParamNull() that you can
use to avoid this problem.
SetFieldNull() in Visual C++ 4.2 was not designed to be called before
calling CRecordset::Open(), and was not designed to handle parameters.
The following files are available for download from the Microsoft
Download Center. Click the file names below to download the files:Paramset.exe For more information about how to download files from the Microsoft Download Center, please visit the Download Center at the following Web address http://www.microsoft.com/downloads/search.aspand then click How to use the Microsoft Download Center. Microsoft has confirmed this to be a bug in the Microsoft products listed at the beginning of this article. The problem has been fixed with Visual C++ version 5.0 by adding a new function called SetParamNull(). MORE INFORMATION
Once you have downloaded Paramset.exe and run the EXE to extract the
CParamSet class files, add CParamSet.CPP to your project. REFERENCESVisual C++ Books Online: CRecordset::SetFieldNull Additional query words: kbVC420bug kbDSupport assert gpf crash
Keywords : kbfile kbDatabase kbMFC kbODBC kbVC kbVC500fix |
Last Reviewed: December 14, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |