• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 233
  • Last Modified:

Access automation call to Outlook failing

An Access database uses Office Automation to create Outlook emails (using late binding). A client has installed Office 2007 (from disk) onto an Asus Windows 8 machine, and is getting the attached error message. I assume the problem is connected with incompatible dll's, but which ones?

Could running in Windows 8 be a problem? Could automatic updates and/or service packs have created incompatible dll's? Are there any diagnostics I can run?
Capture2.PNG
0
slimguy
Asked:
slimguy
  • 5
  • 4
  • 2
2 Solutions
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
First make sure the target machine is fully updated regarding Windows and Office. This sounds more like a hinky install of Office/Outlook than anything else, so if the update doesn't work, try running a Repair of the Office installation.
0
 
slimguyAuthor Commented:
The client has already done an Office Repair - no change.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Can you show the code you're using?

Also - can you verify that you don't have reference issues? A faulty reference can cause lots of troubles - and while you're using Late Binding for this operation, bad references in other libraries can cause Access to choke.
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
slimguyAuthor Commented:
Dim objOutlook As Object
    Dim objEmailMessage As Object
    Set objOutlook = CreateObject("Outlook.Application")
    Set objEmailMessage = objOutlook.CreateItem(0)
   
    l_body = "text here"
   
    objEmailMessage.Recipients.Add "sendsms@messaging.intellisoftware.co.uk"
    objEmailMessage.Subject = smsmessage
    'objEmailMessage.BodyFormat = 1 'Plain text
    objEmailMessage.Body = l_body
   
    objEmailMessage.Display
   
    Set objEmailMessage = Nothing
    Set objOutlook = Nothing

The only references are to VB, Access Object Library, DAO 3.6 Object Library, and one other special one. The db usually crashes immediately if any references are missing.
0
 
Helen FeddemaCommented:
The user may have two versions of Office installed, or just have a different version of Outlook.  I have seen this several times.  Automation code is likely to have problems in this situation.  The solution is to uninstall the various Office versions and do a clean install of one version.
0
 
Helen FeddemaCommented:
What is smsmessage?  If it is a variable, it is not set in your code.
0
 
slimguyAuthor Commented:
smsmessage is string variable set earler. The code is only a partial extract.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Have you added the database location as a Trusted Location?

Also - where is the database installed on the machine? If you're installing to the Program Files directory, you might be running into permissions issues of some sort. On machines with UAC, you must be sure to install the application into an appropriate directory (and that's not Program Files, since an Access "application" is not an executable). If you think this might be an issue, try moving it to a folder in My Documents, or try creating a directory directly off the root drive (like C:\MyApp)
0
 
slimguyAuthor Commented:
It's not in Program Files, it is in a directory off the C drive.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Okay ... but have you added that location as a Trusted Location? 2007 introduced the concept of "Trusted Locations".

See this article for various ways to address that:

http://www.experts-exchange.com/Software/Office_Productivity/Office_Suites/MS_Office/A_10805-Overcome-the-Trust-Center-Nuisance.html
0
 
slimguyAuthor Commented:
I suspect the problem is probably the result of a faulty Office install, or subsequent updates. Repair didn't work. I have decided to avoid the problem by using CDO instead of Outlook (yes, I now it's a cop-out!).
0

Featured Post

The new generation of project management tools

With monday.com’s project management tool, you can see what everyone on your team is working in a single glance. Its intuitive dashboards are customizable, so you can create systems that work for you.

  • 5
  • 4
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now