Skip to main content

[archive] Email with CDO

  • February 24, 2009
  • 3 replies
  • 0 views
D

[Migrated content. Thread originally posted on 23 February 2009]

I create objects with this sintax:
77 wmsmapi-mapisession-handle is handle of MAPISession
of MSMAPI.
77 wmsmapi-mapimessages-handle is handle of MAPIMessages
of MSMAPI.

create MAPISession of MSMAPI
license-key "mgkgtgnnmnmninigthkgogggvmkhinjggnvm"
handle in wmsmapi-mapisession-handle.
create MAPIMessages of MSMAPI
license-key "mgkgtgnnmnmninigthkgogggvmkhinjggnvm"
handle in wmsmapi-mapimessages-handle.

But sending does not work and does not return any message.

With this sintax work!
01 MyMapi.
03 wmsmapi-mapisession-handle MAPISESSION
LINE 01
COL 01
SIZE 03
LINES 03.
03 wmsmapi-mapimessages-handle MAPIMESSAGES
LINE 05
COL 01
SIZE 03
LINES 03.

    3 replies

    D

    [Migrated content. Thread originally posted on 23 February 2009]

    I create objects with this sintax:
    77 wmsmapi-mapisession-handle is handle of MAPISession
    of MSMAPI.
    77 wmsmapi-mapimessages-handle is handle of MAPIMessages
    of MSMAPI.

    create MAPISession of MSMAPI
    license-key "mgkgtgnnmnmninigthkgogggvmkhinjggnvm"
    handle in wmsmapi-mapisession-handle.
    create MAPIMessages of MSMAPI
    license-key "mgkgtgnnmnmninigthkgogggvmkhinjggnvm"
    handle in wmsmapi-mapimessages-handle.

    But sending does not work and does not return any message.

    With this sintax work!
    01 MyMapi.
    03 wmsmapi-mapisession-handle MAPISESSION
    LINE 01
    COL 01
    SIZE 03
    LINES 03.
    03 wmsmapi-mapimessages-handle MAPIMESSAGES
    LINE 05
    COL 01
    SIZE 03
    LINES 03.
    Apparently your license key is invalid. When you do not use license key, the runtime uses the built in ones.
    D

    [Migrated content. Thread originally posted on 23 February 2009]

    I create objects with this sintax:
    77 wmsmapi-mapisession-handle is handle of MAPISession
    of MSMAPI.
    77 wmsmapi-mapimessages-handle is handle of MAPIMessages
    of MSMAPI.

    create MAPISession of MSMAPI
    license-key "mgkgtgnnmnmninigthkgogggvmkhinjggnvm"
    handle in wmsmapi-mapisession-handle.
    create MAPIMessages of MSMAPI
    license-key "mgkgtgnnmnmninigthkgogggvmkhinjggnvm"
    handle in wmsmapi-mapimessages-handle.

    But sending does not work and does not return any message.

    With this sintax work!
    01 MyMapi.
    03 wmsmapi-mapisession-handle MAPISESSION
    LINE 01
    COL 01
    SIZE 03
    LINES 03.
    03 wmsmapi-mapimessages-handle MAPIMESSAGES
    LINE 05
    COL 01
    SIZE 03
    LINES 03.
    Apparently your license key is invalid. When you do not use license key, the runtime uses the built in ones.


    Is what I thought. I removed the reserved word:LICENSE-KEY, but does not work equally.

    I can create objects without including the license-key in a more elegant way?

    Thanks!
    D

    [Migrated content. Thread originally posted on 23 February 2009]

    I create objects with this sintax:
    77 wmsmapi-mapisession-handle is handle of MAPISession
    of MSMAPI.
    77 wmsmapi-mapimessages-handle is handle of MAPIMessages
    of MSMAPI.

    create MAPISession of MSMAPI
    license-key "mgkgtgnnmnmninigthkgogggvmkhinjggnvm"
    handle in wmsmapi-mapisession-handle.
    create MAPIMessages of MSMAPI
    license-key "mgkgtgnnmnmninigthkgogggvmkhinjggnvm"
    handle in wmsmapi-mapimessages-handle.

    But sending does not work and does not return any message.

    With this sintax work!
    01 MyMapi.
    03 wmsmapi-mapisession-handle MAPISESSION
    LINE 01
    COL 01
    SIZE 03
    LINES 03.
    03 wmsmapi-mapimessages-handle MAPIMESSAGES
    LINE 05
    COL 01
    SIZE 03
    LINES 03.
    Apparently your license key is invalid. When you do not use license key, the runtime uses the built in ones.


    Is what I thought. I removed the reserved word:LICENSE-KEY, but does not work equally.

    I can create objects without including the license-key in a more elegant way?

    Thanks!

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement