Effect of DoEvents in Visual Basic OLE Server DLLs

Last reviewed: October 30, 1995
Article ID: Q138063
The information in this article applies to:
  • Professional and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0

SUMMARY

A DoEvents statement inside a inproc OLE server might cause reentrancy problems.

MORE INFORMATION

If you make a call to an inproc OLE server by say, clicking a command button on a form on some client and that call uses DoEvents, Visual Basic will yield to process other pending messages. If now due to some user action another inproc call or the same one is made to the same DLL server, there is nothing to prevent the DLL code from being re-entered. This might cause unforeseen problems depending on the situation, so this scenario is best avoided. Another problem with DoEvents in a DLL is that you are processing messages for the host (.exe file) in your message loop. The host may have special code in its message loop to handle some messages, and problems may occur when this code is not executed.


Additional reference words: 4.00 vb4win vb4all
KBCategory: kbole
KBSubcategory: IAPOLE


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