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

Automating Outlook on a Terminal Server using Access

P: n/a
My client has asked for the ability to send email messages to a list
of users by clicking a button on a form.

This is a piece of cake to provide for our local users who have the
Access application installed on their own machines.

But many of our users access this application remotely using a
Terminal Server. The only way I can think to provide this
functionality for the remote users is to set up Outlook on the
Terminal Server with accounts for each of the users. Then they would
presumably have to log in to Outlook every time they try to send an
email.

Anybody encountered this situation? Any ideas on the best way to
handle it?

Thanks!
Aug 9 '08 #1
Share this Question
Share on Google+
1 Reply


P: n/a
If the program composes the messages and selects the recipients then
using CDO should handle this.
http://www.ffdba.com/downloads/Send_E-Mail_With_CDO.htm

If the users must be able to compose individual messages you could
provide a form on which to do that and still use CDO.

I can see that the many Outlook profiles might be gnarly. I would
probably use gmail accounts and
Application.FollowHyperlink Address As String, [SubAddress As String],
[NewWindow As Boolean = False], [AddHistory As Boolean = True],
[ExtraInfo], [Method As MsoExtraInfoMethod], [HeaderInfo As String]
In this way users could review the e-mail sends whether they were
connected to TS or not.

On Aug 9, 2:46*pm, evenlater <evanca...@gmail.comwrote:
My client has asked for the ability to send email messages to a list
of users by clicking a button on a form.

This is a piece of cake to provide for our local users who have the
Access application installed on their own machines.

But many of our users access this application remotely using a
Terminal Server. The only way I can think to provide this
functionality for the remote users is to set up Outlook on the
Terminal Server with accounts for each of the users. Then they would
presumably have to log in to Outlook every time they try to send an
email.

Anybody encountered this situation? Any ideas on the best way to
handle it?

Thanks!
Aug 10 '08 #2

This discussion thread is closed

Replies have been disabled for this discussion.