MS Outlook intergation with Version 4

Dean_AxonDean_Axon Member Posts: 193
Whilst using version 4 recently, I have noticed that the "allow Access" securtiy box no longer appears. I have checked the "Whats new" and found that the OLHandler.dll file has been fixed.

My questions are these....

Has anyone had the opportunity yet to find out what has been done different by MS that enables v4 to interact without the security window ?

Can I reverse engineer this for previous versions of navision ?

Do i just need to assign the new dll file into my previous versions ?


Dean 8)
Remember: Keep it simple


  • Options
    pdjpdj Member Posts: 643
    I have heard the component has been completely re-written to use Extended MAPI in C++ instead of Simple MAPI in VB. I think the goal was to be able to use the new component instead of the old one. However; I doubt the were able to do it, or it would have been released with 3.70B :-(
  • Options
    Frank_RaemakersFrank_Raemakers Member Posts: 25
    For the previous versions you can use this little programm i found on internet.


    Try it?

  • Options
    Dean_AxonDean_Axon Member Posts: 193
    Hi Frank,

    Have used this before and it works fine. My main concern though is that some other program may try to use my outlook client and this program quite happily allows it to do so as it automatically ticks YES 8-[

    Not too sure on how secure this makes my systems :-k

    Remember: Keep it simple
  • Options
    Dmitry_ChadaevDmitry_Chadaev Member Posts: 52
    Hi Dean,

    You can try Outlook Security Features Administrative Package:

    It is possible to setup trusted applications using it - so that Outlook would treat Navision as its own brother :)

    Read more here:
    http://office.microsoft.com/en-us/assis ... 51033.aspx
    http://gtdsupport.netcentrics.com/downl ... 2XPSP3.pdf
    Best regards,
  • Options
    StyvieStyvie Member Posts: 77

    Just wondered if you ever managed to get this right in a previous version of Navision.

    I have used the new mail codeunit from version 4.0 and successfully used it in Navision 3.7. The only problem I have is that it does not work on machines unless version 4.0 has been installed.

    I have tried to register the OLHanlder.dll and the OLWrapper and the OLaddin file but have not had any luck getting this codeunit to work.... I get the error "Could not create an instance of etc...." as if the automation server is not registered.

    I have checked the virtual table "Automation Servers" on both a machine where version 4.0 has been installed and one where i have registered the controls manually, and the GUID, version , everything looks fine, and the codeunit compiles in Navision 3.7 (on machine where 4.0 has NOT been installed), but I still get the error when trying to send mail...

    Has anybody come right doing this ?
  • Options
    PidiPidi Member Posts: 35
    here is, what I did:

    I registered the OLHandler.dll
    and used the following code


    Name DataType Subtype Length
    OApplication Automation 'NS Outlook Synchronization Handler'.OApplication
    OAttachment Automation 'NS Outlook Synchronization Handler'.OAttachment
    OAttachments Automation 'NS Outlook Synchronization Handler'.OAttachments
    OSendMail Automation 'NS Outlook Synchronization Handler'.OSendMail
    BSTRConverterBody Automation 'Navision Attain Hash 1.0'.BSTRConverter
    BSTRConverterAttachFileName Automation 'Navision Attain Hash 1.0'.BSTRConverter
    HideDialog Boolean
    ErrorNo Integer


    NewMessage(ToName : Text[80];CCName : Text[80];Subject : Text[260];Body : Text[260];AttachFileName : Text[260];OpenDialog : Boolean) MailSent : Boolean

    IF ISCLEAR(OApplication) THEN

    IF (NOT OApplication.Logon(TRUE,'','',FALSE,FALSE)) THEN BEGIN



    ErrorNo := 0;

    OSendMail."To" := ToName;
    OSendMail.CC := CCName;
    OSendMail.Subject := Subject;

    IF ISCLEAR(BSTRConverterBody) THEN

    IF Body <> '' THEN BEGIN
    OSendMail.Body := BSTRConverterBody;

    IF ISCLEAR(BSTRConverterAttachFileName) THEN

    IF AttachFileName <> '' THEN BEGIN
    OAttachments := OSendMail.Attachments;
    OAttachment := OAttachments.Add(BSTRConverterAttachFileName);

    OSendMail.OpenDialog := OpenDialog; // if parameter is FALSE, the mail will be sent without any kind of message or alert !

    MailSent := OSendMail.Send;
    ErrorNo := OSendMail.ErrorStatus;

    surprisingly pretty simple.
    Unfortunately I have no idea, what the BSTRConverter AC is good for,
    and no time yet, to figure it out.

    Michael Peters
    Bos Fod GmbH Düsseldorf
    +49 2132 139-0
  • Options
    PidiPidi Member Posts: 35
    Ooops - forgot to mention, that I used the described function from within
    an Attain 3.6 environment.

    Michael Peters
    Bos Fod GmbH Düsseldorf
    +49 2132 139-0
Sign In or Register to comment.