Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 714
  • Last Modified:

Access 2007 on WinServ2008Standard - SendObject comes up with allow/deny

Access 2003 (MDB) database using SendObject command.  Works fine on an old XP box running Office 2003 apps and ClickYes, connecting to Exchange Server 2007.

Moving apps to a new box running Windows Server 2008 Standard and Office 2007.
SendObject command keeps popping up with the "allow/deny" sending of the e-mail message.  Have set up Trust Center in Access/Outlook to allow macros, programmatic access, etc....still doesn't work.  

Any suggestions on how to eliminate that allow/deny popup?
0
ParisBP
Asked:
ParisBP
  • 4
2 Solutions
 
fhlio_adminCommented:
It is Outlook Security...

Try an app like MapiLabs

http://www.mapilab.com/outlook/security/
0
 
ParisBPAuthor Commented:
Thanks for the suggestion.  I installed their Advanced Security for Outlook yesterday even though WinServ2008Standard is not listed in their system requirements...did not work.  When trying to run the task (WinServ task scheduler, calls the Access macro via commandline switches) *OR* manually executing the macro in Access itself, I never received a prompt from the MAPILab application to set the allow/deny access value as indicated in the small graphic at the top of that webpage.

Sidenote - within Outlook 2007's Programmatic Access, message appears as "Antivirus status:  unavailable.  This version of Windows does not support antivirus detection".  We're running Symantec Enpoint Protection and the machine is considered isolated...so punching holes in the registry to get the messages out is certainly an acceptable option.  Tried a couple of entries that I saw elsewhere, but they didn't work either (to reg key location HKLM/SOFTWARE/Microsoft/Office/12.0/Outlook/...)

Another option (?) - uninstall Outlook 2007 and install Outlook 2003...don't know about potential for version conflicts...
0
 
dzaldivarCommented:
If you can upgrade to Access 2007 you can use the "CreateObject("Outlook.Application")" and it bypasses the Outlook "allow/deny popup".

Dave
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 
ParisBPAuthor Commented:
We're using Access/Outlook 2007 already...running on WinServ2008Standard.  Connecting to Exchange Server 2007.  All of our automation is running straight off pure Access macros...no VBA.  Outlook is open/minimized at all times.  I threw out the idea of switching Outlook back to 2003 if there were no complications.  Just throwing ideas at the wall now, trying to see what'll stick.  Thanks for the response.
0
 
ParisBPAuthor Commented:
Have also tried making registry changes as suggested on Microsoft site for
[HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\12.0\Outlook\Security] and DWORDS (value 2 for autoapprove) on PromptSimpleMAPISend, PromptSimpleMAPINameResolve and PromptSimpleMAPIOpenMessage.

As mentioned above, we are on Access/Outlook 2007 (32 bit, connecting to Exchange Server 2007) and Windows Server 2008 Standard (64 bit).

Running out of guesses and time...
0
 
ParisBPAuthor Commented:
Opted to go with ClickYes Pro...seems to work fine for what we're looking to do.  
Thanks to those who responded.
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

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