How Server Use Is Determined by OLE

 Last reviewed: February 9, 1996
Article ID: Q145700
The information in this article applies to:
  • Standard, Professional, and Enterprise Editions of Microsoft Visual Basic, 16-bit and 32-bit, for Windows, version 4.0

SUMMARY

When an OLE Automation client requests an object that can be provided by more than one server, OLE uses a predefined set of rules to determine which server is used to supply that object. This article lists the order used by OLE when providing objects.

MORE INFORMATION

Each object that can be provided to an OLE Automation client can be identified by an unique 64-bit number called a CLSID. The system registry contains a key called CLSID (immediately off of HKEY_CLASSES_ROOT), which has as subkeys every CLSID registered on the system. The subkeys of each CLSID hold information for each object, including the path and filename of the server(s) that can be used to provide that object, according to this table: 

   Key               Server
   ---------------------------------------------------------------------
   InprocServer      16-bit DLL (in-process) server
   InprocServer32    32-bit DLL (in-process) server
   OutprocServer     16-bit EXE (out-of-process) server
   OutprocServer32   32-bit EXE (out-of-process) server
It is possible (and completely allowed by OLE) to have more than one of the above keys beneath a given CLSID. If this situation occurs, OLE uses a predefined order to determine which server is used to provide an object. This decision is based both on the bitness of the potential OLE Automation client and the bitness of the operating system. OLE uses this order:

  1. In-process (DLL) server of same bitness as the client
2. 32-bit local server (only for 16-bit clients on a 32-bit OS) 3. Out of process server of same bitness as client 4. Out of process server of other bitness as client

Additional reference words: 4.00 vb4win vb4all
KBCategory: kbprg kbole
KBSubcategory: APrgOther

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