FIX: GPF/UAE When Assign NULL to VBM_GETPROPERTY of type HLSTD

Last reviewed: October 30, 1997
Article ID: Q94217
2.00 WINDOWS kbtool kbbuglist

The information in this article applies to:

- Microsoft Visual Basic programming system for Windows, version 2.0

SYMPTOMS

When you return a NULL in response to the VBM_GETPROPERTY message for a custom property of data type HLSTR, a General Protection (GP) fault or Unrecoverable Application Error (UAE) occurs.

Because of this problem, you cannot simply use the PF_fGetData flag with a custom property of data type HLSTR. What's more, you must use the PF_fGetMsg flag to ensure that the value of the property is never set to NULL. This information is taken from the CDK.TXT file provided with Microsoft Visual Basic Professional Edition version 2.0 for Windows.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Visual Basic Professional Edition version 2.0 for Windows. This problem was corrected in Microsoft Visual Basic version 3.0 for Windows.

MORE INFORMATION

Below is the information provided in the CDK.TXT file:

DT-HLSTR Properties and PF_fGetData

DT_HLSTR properties cannot use PF_fGetData by itself. They must also use PF_fGetMsg to avoid returning a NULL hlstr. See the MyTag property in the PIX example (PIX.C) for a guide for how to properly declare a HLSTR property and process the VBM_GETPROPERTY message.


Additional reference words: 2.00 3.00 buglist2.00 fixlist3.00
KBCategory: kbtool kbbuglist
KBSubcategory: TlsCDK
Solution Type : kbfix


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: October 30, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.