This article was previously published under Q319660
This article has been archived. It is offered "as is" and will no longer be updated.
The COleVariant constructor, COleVariant(long lSrc, VARTYPE vtSrc = VT_I4), does not correctly initialize its members. As a result, when you call the CDaoTableDef::CreateField member function, you receive a CDaoException exception with the following call stack:
This problem occurs because the constructor initializes members based on an uninitialized member. As a result, the vt member of COleVariant may be initialized to the VT_UI4 or the VT_HRESULT variant type instead of the VT_I4 variant type.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Visual Studio .NET service pack that contains this hotfix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name Platform --------------------------------------------------------------- 26-Mar-2002 10:04 7.00.9480.0 974,848 Mfc70.dll x86 26-Mar-2002 09:19 7.00.9480.0 1,933,312 Mfc70d.dll x86 26-Mar-2002 09:53 7.00.9480.0 964,608 Mfc70u.dll x86 26-Mar-2002 09:22 7.00.9480.0 1,927,680 Mfc70ud.dll x86 28-Mar-2002 06:01 none 850,944 VC_MFC.msm none
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.