HOWTO: Make a Typelib (.TLB) File for ActiveX Components

Last reviewed: March 17, 1997
Article ID: Q161272
The information in this article applies to:
  • Microsoft Visual Basic Professional and Enterprise Editions, for Windows, version 5.0

SUMMARY

When you create an ActiveX component (OLE server) using Visual Basic, a separate typelib (.TLB) file is not generated automatically. By default, the type library for the ActiveX component is compiled into the .EXE or .DLL file. If you are using the Professional or Enterprise editions of Visual Basic 5.0, you can create a typelib file for any non-private ActiveX .EXE (out-of-process OLE server) and any non-private ActiveX .DLL (in-process OLE server).

MORE INFORMATION

Step-by-Step Example

  1. Open your ActiveX EXE or ActiveX DLL project. (If you need to create an ActiveX EXE or ActiveX DLL project for the first time, see the "Component Tools Guide," "Creating ActiveX Components," "Creating an ActiveX DLL," or "Creating an ActiveX EXE Component" for more information.)

  2. From the Project menu, click "<ProjectName> Properties..." where <ProjectName> is the name of your project.

  3. Click the Component tab. Check (select) the option for Remote Server Files. Note that this option is enabled only if you are creating an accessible ActiveX component (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.

  4. Click OK.

  5. From the File menu click "Make <ProjectName>.exe..." or "Make <ProjectName.dll...".

When you compile your ActiveX component (OLE server), a .VBR file (which is a modified .REG file) and a .TLB file will be created.


Keywords : kbusage vb5all vb5howto VBKBAutomation VBKBAX VBKBComp VBKBDLL kbhowto
Technology : kbole
Version : 5.00
Platform : WINDOWS
Issue type : kbhowto


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