Skip to main content

Error creating ActiveX control

  • August 15, 2012
  • 1 reply
  • 0 views
D

We have been using a 3rd-party product to called Outlook Security Manager to bypass Outlook's security warning messages when generating emails.  Since upgrading to their latest version, we've been getting "Error creating ActiveX control" messages.  I've posted to their forums, too, but I think their Cobol knowledge is limited so I thought I'd try here as well.

The object is defined as:

 01 OSM-SCREEN.
    03 HOutlookSM       OutlookSecurityManager
           LINE    1
           COL     1
           LINES   1
           SIZE    1
           VISIBLE 0.

and then instantiated by:

     DISPLAY OSM-SCREEN.

This is the point at which the error occurs.  I'm unsure about whether this is an installation issue, a security issue, a licensing issue, or a Cobol issue.  Any ideas?

    1 reply

    Stephen Hjerpe
    • Stephen Hjerpe
    • Participating Frequently
    • 1100 replies
    • August 20, 2012

    We have been using a 3rd-party product to called Outlook Security Manager to bypass Outlook's security warning messages when generating emails.  Since upgrading to their latest version, we've been getting "Error creating ActiveX control" messages.  I've posted to their forums, too, but I think their Cobol knowledge is limited so I thought I'd try here as well.

    The object is defined as:

     01 OSM-SCREEN.
        03 HOutlookSM       OutlookSecurityManager
               LINE    1
               COL     1
               LINES   1
               SIZE    1
               VISIBLE 0.

    and then instantiated by:

         DISPLAY OSM-SCREEN.

    This is the point at which the error occurs.  I'm unsure about whether this is an installation issue, a security issue, a licensing issue, or a Cobol issue.  Any ideas?

    Did this syntax work in the previous version of Outlook Security Manager? If so, what has changed in the Outlook Security Manager ... is it still an ActiveX control, is there licensing involved, has it become a .Net assembly? What error do you receive?


    Terms & ConditionsAccessibility statement