How to Get a Typelib (.TLB) File for a VB 4.0 OLE Server

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

SUMMARY

When you create an OLE server (.EXE or .DLL) using Visual Basic 4.0, a separate Typelib (.TLB) file is not automatically created. By default, the type library for the OLE server is compiled into the executable or .DLL file. It is possible to have Visual Basic create this file for your OLE server if you are using the 32-bit version of the Enterprise Edition of Visual Basic (for 32-bit in-proc OLE servers) and either the 16-bit or 32- bit version of the Enterprise Edition of Visual Basic (for 16-bit or 32-bit local OLE servers).

MORE INFORMATION

With the Enterprise edition of Visual Basic 4.0, open the Make OLE DLL file dialog (32-bit only) or the Make EXE file dialog (16-bit or 32-bit) by choosing the corresponding menu item from the File menu. In the dialog, click the Options button. In the Options dialog, select the "Remote Server Support Files" check box. This will generate a .VBR (which is a modified .REG file) and a .TLB for your OLE server.

Note that this check box will be enabled only if you are creating an accessible OLE server with your current project, that is only if you have at least one Class Module in the project whose Public property has been set to True.


Additional reference words: 4.00 vb4win vb4all vbctrl
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.