Mastering PowerBuilder

HomePrevious Lesson: In-Process Versus Out-Process
Next Lesson: Windows Registry

OLE Automation - PowerBuilder Implementation

In previous sections, you have learned how to make use of Microsoft word 6.0 OLE server for various needs such as 'find and replace' a specific word. Similarly, you can also create PowerBuilder's OLE server and allow any OLE client applications to make use of PowerBuilder functionality. PowerBuilder implements OLE Automation Server as in-process, i.e., makes use of the calling application's (OLE Client) memory. You can make use of any Non-Visual user object to create PowerBuilder OLE Automation Server. The following are the steps that are involved in creating a PowerBuilder OLE Automation Server.

You have learned about creating non-visual user objects in the "User Objects" session. So, let's skip to second step.

Every OLE Server Object should register its identity with the operating system (Windows), then only operating system can supply all the available OLE server object names when you browse for the valid OLE Servers in the OLE Client application. Similar to the Social-Security number each person has in USA, all OLE Server Objects have a number called GUID (Globally Unique Identifier). GUID is also referred as UUID (Universally Unique Identifiers), CLSID (Class ID).

Before we explore PowerBuilder's OLE Automation Server implementation, it would be better to understand fully about windows Registry, since you need to deal with the registry in the development as well as at OLE Server installation time.
HomePrevious Lesson: In-Process Versus Out-Process
Next Lesson: Windows Registry