BUG: OLE SUBCLASS: Subclassing of OleControl/OLE Unspecified

 Last reviewed: May 5, 1997
Article ID: Q134215
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, versions 3.0, 3.0b, 5.0, 5.0a

SYMPTOMS

When an OleControl is subclassed, the following error message appears in Visual FoxPro 3.0 and 3.0b: 

   OLE error code 0x80004005: Unspecified error.
Visual FoxPro 5.0 generates this error message: 

   Object class is invalid for this container.

WORKAROUND

Create a new class with the name you want based on the subclass that was just created.

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

MORE INFORMATION

Steps to Reproduce Problem

  1. To create a new class, type the following code in the Command window:

    CREATE CLASS comm1 OF comms AS olecontrol

  2. From the Control Type list box, select Microsoft Comm Control.

  3. Click the Insert Control option button, and choose OK.

  4. When the Class Designer comes up, save and close the new class.

  5. To try to rename the new class, type the following in the Command window:

    RENAME CLASS comm1 OF comms TO mycomm

At this point, Visual FoxPro generates the error.

Additional query words: OLE control
Keywords : buglist3.00 buglist3.00b buglist5.00 kberrmsg vfpbug5.0a kbbuglist
Version : 3.0 3.0b 5.0 5.0a
Platform : WINDOWS
Issue type : kbbug

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: May 5, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.