[AccessD] email from outlook

Gustav

...afaik, and it isn't very far, MAPI is the closest thing to a universal 
e-mail protocol available ...if the client has e-mail capability installed, 
most (not all ala Lotus) modern e-mail clients respond to MAPI without 
further intervention on my part ...and I can send from vba without the user 
being involved except as I want them to be ...I don't have to know what the 
client is nor anything about it except that its MAPI compliant ...SMTP otoh 
always requires some sort of client configuration.

...but like you said, it really depends on the user environment ...while 
MAPI will work in probably 90% or better of user systems, there are always 
going to be those running Lotus Notes or some other non-standard e-mail 
client ...thus JC's search for a one-size-fits-all solution is, imnsho, 
going to wind up with a one size fits most.

William

----- Original Message ----- 
From: "Gustav Brock" <Gustav at cactus.dk>
To: <accessd at databaseadvisors.com>
Sent: Monday, June 19, 2006 7:20 AM
Subject: Re: [AccessD] email from outlook


> Hi John
>
> That leaves you with CDO (cdosys.dll) which on the other hand is extremely 
> powerful:
>
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cdosys/html/ecdb51f4-5ba0-46d8-9c7c-7e4154a18f50.asp
>
> A real yummy for class nerds like you. Installed by default from Win 2000 
> and up.
> You will note the menu. Visit Developing Environment and Messaging.
>
> Unless the client has an Exchange server you can pass your mail to, you 
> will have to specify an SMTP server to actually send your mail. That can 
> be a small SendMail util installed on the workstation (but you didn't want 
> that), the SMTP service of IIS - which may be installed and active on the 
> workstation but most often is not, or on the server but with no access for 
> the workstations. Or it can be the SMPT server in use by the client (which 
> will be different for each client, thus your app will not know the name) 
> or an external SMTP which will allow relaying and thus authentication 
> (could be run by yourself on an old machine with, say, Mercury/32 server). 
> But for the last two cases port 25 outbound must not be blocked on neither 
> the workstation nor the corporate firewall which it quite often is.
>
> So, whatever CDO can do for you, you cannot define yourself out of 
> potential trouble. What you can perform on a client's machine is really up 
> to the network administrator. And if the client uses a locked down system 
> with, say, Lotus Notes and no Internet access, your only chance may be 
> MAPI.
>
> /gustav
>
>>>> jwcolby at colbyconsulting.com 19-06-2006 05:00:47 >>>
>
> I need: A piece of code, written in Access VBA, that will send an email
> message, complete with an attachment, regardless of where the Access
> Application is installed, regardless of what email client the application 
> or
> computer user normally uses.  It must NOT require installation of a DLL,
> knowledge of a specific email client, calls to methods of a specific email
> client, reference to a library (unless that library is ALWAYS available on
> EVERY Windows computer).
>
> I don't ask for much, just email.  ;-)
>
> John W. Colby
> Colby Consulting
> www.ColbyConsulting.com
>
>
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com