Client-side Registry Entries for Business Objects with DCOM

Custom business objects need to ensure that the client side can map their program name (ProgId) to an identifier (CLSID) that can be used over DCOM. For this reason, the ProgID of the DCOM object must be in the client side registry and map to the class ID of the server-side business object. For the other supported protocols (HTTP, HTTPS, and in-process), this isn't necessary.

For example, if you expose a server-side business object called MyBObj with a specific class ID, for instance, "{00112233-4455-6677-8899-00AABBCCDDEE}", you should make sure the following entries are added to the client-side registry:

[HKEY_CLASSES_ROOT]
\MyBObj
   \Clsid
   (Default) "{00112233-4455-6677-8899-00AABBCCDDEE}"

DCOM Stream Marshaling

A client computer using RDS 1.5 or prior components is not compatible with a server using RDS 2.0 components. The newer RDS 2.0 support is more efficient in transporting Recordset objects. If this is the case, you can set your server to work with the previous RDS support (called RDS 1.0) or the newer RDS support (called RDS 2.0). Set either of the following registry entries:

[HKEY_CLASSES_ROOT]
\CLSID
   \[58ECEE30-E715-11CF-B0E3-00AA003F000F}
      \ADTGOptions]"MarshalFormat"="RDS10"

-or-

[HKEY_CLASSES_ROOT]
\CLSID
   \[58ECEE30-E715-11CF-B0E3-00AA003F000F}
      \ADTGOptions]"MarshalFormat"="RDS20"