By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,952 Members | 985 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,952 IT Pros & Developers. It's quick & easy.

How can we control the security pop-ups when Automating OPutlook from Access?

P: n/a
Hi folks,

We have an Access 2000 app that is highly integrated with Outlook 2000
or later. The app allows the user to send predefined emails that are
created through an Access form and stored in a table bound to that
form.

It all works great EXCEPT for one thing: Every time the user
generates an email message to be placed into the Outlook outbox,
Outlook pops up a message that requires the user to allow "another
program" to insert a message into Outlook (Yes/No).

Is there any way to stop this? It's very annoying to our users. It
REALLY gets annoying when they use our "Send email to a filtered group
of records" feature because it stops on EACH message and requires user
confirmation. If you're sending 50 or a hundred messages, it slows
the whole process down to the point where our group send feature is
less valuable.

In the long term, we will install an SMTP engine into the app and
totally bypass Outlook for the purpose of group mailing. But we'll
still want to use Outlook for sending one message at a time.

Any useful advice on this will be much appreciated.

Thanks,
--LW
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
Lauren Wilson <???@???.???> wrote:
It all works great EXCEPT for one thing: Every time the user
generates an email message to be placed into the Outlook outbox,
Outlook pops up a message that requires the user to allow "another
program" to insert a message into Outlook (Yes/No).
See the Outlook specific links at the Access Email FAQ at my website.
http://www.granite.ab.ca/access/email/outlook.htm
In the long term, we will install an SMTP engine into the app and
totally bypass Outlook for the purpose of group mailing. But we'll
still want to use Outlook for sending one message at a time.


The best solution here would be to use TCP/IP stuff directly. With no versioning
problems, etc.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Nov 13 '05 #2

P: n/a
On Fri, 10 Sep 2004 18:14:18 GMT, Tony Toews <tt****@telusplanet.net>
wrote:
Lauren Wilson <???@???.???> wrote:
It all works great EXCEPT for one thing: Every time the user
generates an email message to be placed into the Outlook outbox,
Outlook pops up a message that requires the user to allow "another
program" to insert a message into Outlook (Yes/No).


See the Outlook specific links at the Access Email FAQ at my website.
http://www.granite.ab.ca/access/email/outlook.htm


Thanks Tony.
In the long term, we will install an SMTP engine into the app and
totally bypass Outlook for the purpose of group mailing. But we'll
still want to use Outlook for sending one message at a time.


The best solution here would be to use TCP/IP stuff directly. With no versioning
problems, etc.


This comment confuses me. Exactly what do you mean by
"use TCP/IP stuff directly"?

I am testing a number of SMTP engines that can be used with VBA code.
What are the most common pitfalls for programmers attempting such a
thing?

Again Tony, you're a dear man. Thanks very much for your help.

--LW
Nov 13 '05 #3

P: n/a
Lauren Wilson <???@???.???> wrote:
The best solution here would be to use TCP/IP stuff directly. With no versioning
problems, etc.
This comment confuses me. Exactly what do you mean by
"use TCP/IP stuff directly"?


I should've use the proper terminology. I should've stated Winsock. You can hit
the Windows sockets directly yourself without using any external SMTP engines. See
http://www.granite.ab.ca/access/email/winsock.htm
I am testing a number of SMTP engines that can be used with VBA code.
What are the most common pitfalls for programmers attempting such a
thing?


Versioning and distribution. By that I mean the user is going to have to somehow
install the DLL/EXE associated with that SMTP engine on their system. That could be
interesting if all you want to distribute is an MDB/MDE.

Also with SPF/Sender ID becoming more popular you may find that you can no longer
send emails directly to receiving mail servers. The user may have to logon to their
own (or ISPs) mail server and send email via the email server. This is likely the
case right now but I thought I'd better mention it.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.