Using Outlook Redemption with Extend COBOL

Hi-

After struggling for years with MapiLand and Outlook Security Manager in our Extend ACUCOBOL applications, we have decided to replace both with Outlook Redemption. It works very well with one exception: If Outlook is not actively running on the workstation, use of Redemption results in a Memory Access Violation Fatal COBOL error. 

Has anyone else had this issue and if so how did you solve it?

  • Sal, you have this:

          DECLARATIVES.

          OBJECT-EXECEPTION-HANDLING SECTION.

              USE AFTER EXCEPTION ON OBJECT.

          OBJECT-EXCEPTION-HANDLER.

              CALL      "C$EXCEPINFO"            USING  ERROR-INFO

                                                        ERR-SOURCE

                                                        ERR-DESCRIPTION

                                                        ERR-HELP-FILE

                                                        ERR-HELP-CONTEXT.

          END DECLARATIVES.

  • Verified Answer

    Jaap-

    Thank you for replying. Yes, we do use the Declaratives as you suggest. But that was not the solution.  It turned out that when Redemption is called it generates an error when Outlook is not running, and the error was reported as a MAV error in v9.0 wrun32.  Our solution was two part: First we upgraded wrun32 to version v9.1.2.1 and the MAV error was replaced by something  usable. When we understood that we were then able to use the Windows TASKLIST utility to test whether Outlook was running before calling Redemption.

    I would like a more elegant way to determine if Outlook is running, but otherwise I am satisfied with the solution.

    Regards,

    Sal