How To Manually Register a VB Remote Component Using CLIREG32 (194636)



The information in this article applies to:

  • Microsoft Visual Basic Enterprise Edition for Windows 5.0
  • Microsoft Visual Basic Enterprise Edition for Windows 6.0

This article was previously published under Q194636

SUMMARY

This article demonstrates how to use the CLIREG32.EXE utility to manually register remote Visual Basic components on the client machine.

To use the Clireg32 utility, you must have created the remote server files (VBR and TLB files) when you compiled your server component. To have Visual Basic create these files, go to Project Properties Component Tab, and then select the Remote Server Files option.

MORE INFORMATION

WARNING: One or more of the following functions are discussed in this article; VarPtr, VarPtrArray, VarPtrStringArray, StrPtr, ObjPtr. These functions are not supported by Microsoft Technical Support. They are not documented in the Visual Basic documentation and are provided in this Knowledge Base article "as is." Microsoft does not guarantee that they will be available in future releases of Visual Basic.

You use the method that follows to manually register the remote component.

NOTE: However, before doing this, you need to copy the VBR and TLB files to a directory on the client computer.

Use the Clireg32 utility from a command line. To register your remote component from a command line, use the following syntax and options:

       
    CliReg32 {path to the VBR file} -s SERVERNAME -t {path to the TLB file)   
            -d -q
    -s = Remote server name
    -t = Type library file name
    -d = Use DCOM as the remote transport
    -q = Suppress all dialogs 

					
Other command line options available include:
  
    -l = Specifies a log file
    -u = Uninstall VBR file
    -a = Set authentication level (0 - 6)
    -p = Network protocol
    -nologo = Do not display copyright information
					

REFERENCES

Hardcore Visual Basic, second edition by Bruce McKinney

Modification Type:MinorLast Reviewed:3/7/2005
Keywords:kbClient kbDCOM kbhowto kbServer KB194636