How To Use Clireg32.exe for Remote Automation

 Last reviewed: January 20, 1997
Article ID: Q155939
The information in this article applies to:
  • Microsoft Visual FoxPro for Windows, version 5.0

SUMMARY

This article provides an explanation of Clireg32.exe and how it is used for remote automation.

MORE INFORMATION

The Clireg32.exe component allows you to register an OLE server (.exe) remotely. It differs from the Remote Automation Connection Manager (RacMan) in that the server does not need to be located on the machine registering it. The Setup Wizard handles the maintenance of registering remote servers for you.

NOTE: Remote servers and Clireg files are stored in the \Windows\Olesrv\ directory, which is similar to Visual Basic if it is installed via the Setup Wizard.

The Clireg32.exe program takes a number of parameters. The only required one is the name of the .vbr file (generated with the server during build): 

   Clireg32 myexesvr.vbr
In order to fully register a remote server, you must provide the network name, network protocol, and security access. Clireg32 prompts you with a dialog box if these options are not passed. For a list of all the parameters, simply execute Clireg32.exe by itself.

KBCategory: kbole kbusage kbprg kbhowto
KBSubcategory: FxinteropOle
Additional reference words: 5.00 kbdse VFoxWin



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