Search results

  1. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    thank you all for your help though - should this ever get resovled i have a multitude of code options for this.
  2. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    Looking 99% percent positive its our security systems. My simple question started an avalanche of complaints against IT (whoops) - need to find the time to see if i can a. circumvent outook or b. convince IT to reverse their crazy decision.
  3. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    because we are using 365 i am now trying to circumvent their security settings aorund outlook by using CDO. not hopeful at present. looks more and more like its my IT security not enabled automation in outlook in windows 10 even though they allowed it in windows 7
  4. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    doesnt move to the .send command until the .display is dealt with - then errors. guessed it would but happy to try just about anything.
  5. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    send object worked with the 5sec countdown
  6. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    copied code to new module. changed the end olmail to end with as was giving me syntax error fails at same point - .send really starting to wonder if our security settings in 365 are preventing .send
  7. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    fail: it struggled at this .Importance = olImportanceHigh 'High importance so i disabled but still failed at the .send
  8. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    yes - it is always running (always watching ;))
  9. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    no - did i miss that suggestion?
  10. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    ok - still getting the crash out at the .send stage. here is the current code Const olMailItem = 0 Public Sub SendMailboxHTMLMessage(DisplayMsg As Boolean, WhoTo As String, WhoCC As String, Mailbox As String, TheSubject As String, TheBody, Optional AttachmentPath) Dim objOutlook As Object...
  11. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    will hit the ground running first thing tomorrow - thanks for allyour help so far!
  12. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    just did - reckon i have implemented it wrongly.... Public Sub SendMailboxHTMLMessage(DisplayMsg As Boolean, WhoTo As String, WhoCC As String, Mailbox As String, TheSubject As String, TheBody, Optional AttachmentPath) Dim objOutlook As Object 'Outlook.Application Dim objOutlookMsg As Object '...
  13. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    Getting: Compile Error Invalid or unqualified reference
  14. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    trying these but i am getting the errors related to wrong SMTP settings (maybe more) - i have asked some of my IT dept buddies if they can assist.
  15. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    Another example that looks amazing but uses the password part. I doubt they will ever allow that but i have no idea of the password for a shared mailbox on 365. if there is one - its not something i see - everything just appears to use my microsoft account (sorry not very technical)
  16. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    i have tried but have less experience with CDO and im convinced im doing it wrong. what would be the CDO equivelent?
  17. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    .display does work but breaks the process. most of the .send processes are becuase we need it to automatically email once something has been imported. if using .display then we risk it not being sent or being altered accidently.
  18. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    i get this at the .send stage in 365/64bit same database and code in 2016/32bit - no issue
  19. D

    VBA Code to email (outlook) - Fine in 2016(32bit) / Broken in 365(64bit)

    We are running MS Exchange - and there are plenty of complaints at the new security level concerning macro's etc. Not sure i am going to get anywhere on those issues as the company likes thenew security level (for some strange reason) Not sure what an STIG is :) the .Send part is where i get...
Top Bottom