The information in this article applies to:
SUMMARYThis article discusses the registry settings required for OLE Automation and how to set them if you do not use the Setup Wizard. MORE INFORMATION
OLE Automation works if you install a product correctly or you use the
Setup Wizard (assuming you choose an OLE Server).
Local AutomationYou do not need extra files for remote automation except for the servers themselves. Primarily, you need the Oleaut32.dll file, which is installed by Visual FoxPro, the Setup Wizard, and Windows.Registering OLE Servers LocallySimply building an OLE server (.exe or .dll file) via the Project Manager or BUILD command automatically registers the server on that machine. If you want to copy the OLE server to another machine (not via the Setup Wizard) and register it, you should do the following:
Remote AutomationRemote automation requires several components in addition to the server files to work correctly, including the following Automation Proxy and Automation Manager files:
Registering OLE Servers LocallyThere are several ways to register a remote automation server. The easiest is to use the Remote Automation Connection Manager (RacMan). You must first have the server registered locally. RacMan uses the following files:
You can also use the Clireg32.exe component to register a server remotely.
All that is required to use the Clireg32.exe component is the .vbr file.
Updating a ServerIt is always a good idea to reregister a server when you update it. If you are using the Project Manager, the BUILD EXE command, or the BUILD DLL command, the server is automatically updated on that machine.NOTE: You can choose the Generate New Registry IDs option to re-create new GUIDs for the server settings. You can reregister servers on other remote machines using the techniques described above. These techniques include the Setup Wizard, the RacMan component, the RegSvr32 component, and the CliReg32 component. Additional query words: register CLIREG32 Remote Local
Keywords : kbinterop kbAutomation |
Last Reviewed: August 2, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |