How to Optimize Remote OLE Automation Performance

Last reviewed: July 15, 1996
Article ID: Q153568
The information in this article applies to:
  • Enterprise Edition of Microsoft Visual Basic for Windows, 32-bit only, version 4.0

SUMMARY

Remote OLE Automation involves cross-machine calls across a network, which can really slow things down, so it is important to keep a few things in mind while making such remote calls. This article lists the ways in which you could optimize the performance of your remote calls.

MORE INFORMATION

First, always use Early Binding. This reduces the number of calls between objects by about 50%. This can make a big performance difference when remoting objects (especially over RAS). The only time you should use late binding is if you do not know ahead of time what the object is that you will be connecting to.

Second, when calling methods on objects, create a method that accepts 'n' number of parameters than exposing 'n' properties on the object, setting each, and then calling the method. This is faster because the OLE call is the more expensive part in terms of execution time. Passing relatively large amounts of data within the call works well. The one limitation to keep in mind while doing this is that if you are using a 16-bit object, you can't pass more than 64k of data at one time.


Additional reference words: 4.00 vb4win vb432
KBCategory: kbusage kbole kbhowto
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: July 15, 1996
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.