BUG: @ .. SAY Gives Error: Invalid or Corrupt OLE Object

Last reviewed: June 26, 1995
Article ID: Q122971
The information in this article applies to:
  • Microsoft FoxPro for Windows, versions 2.5, 2.5a, 2.5b, 2.6, 2.6a

SYMPTOMS

Issuing a series of @..SAYs from a general field containing a bitmap results in this error message:

   Invalid or Corrupt OLE Object

CAUSE

Issuing several @..SAYs to display a bitmap from a general field causes this error because approximately 32 bytes of memory are lost each time a bitmap is displayed. Memory is not being released properly. After several @..SAYs, FoxPro eventually runs out of resources.

RESOLUTION

Issue an @..SAY..BITMAP from a file instead of a general field.

MORE INFORMATION

Steps to Reproduce Problem

  1. Create a database with a general field called Gen.

  2. Append a blank record to the new database and copy a bitmap into the general field.

  3. Type in and run the following program to reproduce the problem:

    endit=.F.

    ON KEY LABEL F10 endit=.T. DO WHILE endit != .T.

          @ 0,0 SAY gen
    
    ENDDO

After several iterations, the error message is displayed.


Additional reference words: FoxWin 2.50 2.50a 2.50b 2.60 2.60a buglist2.50
buglist2.50a buglist2.50b buglist2.60 buglist2.60a
KBCategory: kbinterop kbole kbbuglist
KBSubcategory: FxinteropOle


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: June 26, 1995
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.