[AccessD] AccessD Digest, Vol 84, Issue 21

Gustav Brock Gustav at cactus.dk
Tue Feb 16 01:42:53 CST 2010


Hi Ken

You may be right. I can see my code references CDOEX, and using CDO under Vista (and so Windows 7, I guess) can be a mess:

http://www.vbforums.com/showthread.php?t=560446
http://msdn.microsoft.com/en-us/library/ms978698.aspx
http://support.microsoft.com/kb/171440

So I'm in doubt what to do or recommend. Or maybe not - the last applications I've made, where sending mail is a part of the functionality, were programmed in .Net/VS2008/C# where all this stuff is native and very easy to get up and running.

The FMS tool will most likely work if you have the budget. If not, I would have a second look at the VB dll mentioned by Stuart ... depends a little of your requirements and how much user interaction is requested.

/gustav


>>> kismert at gmail.com 16-02-2010 00:09 >>>
Gustav Brock:

> ... If you don't want to install anything, I can recommend using the native
> Windows CDO component which is installed by default on any newer Windows
> ...
>


Gustav:

This version of CDO is easy to use, but I have two reservations:

1) I can't tell from the docs whether it is installed on Vista and Windows 7
(MS has ceased distributing the COM-based MAPI libraries for Outlook, also
called CDO).

2) When I referenced cdosys.dll, my A2K front-end stopped working. Removing
it fixed the problem. Changing the priority of cdosys in the references list
fixed it, but only until the next code change, where you would have to do it
again. A major PITA. Your mileage may vary.

Can you verify that the Microsoft CDO for Windows 2000 Library
(C:\Windows\System32\cdosys.dll) is installed on Vista and Windows 7
machines?

-Ken





More information about the AccessD mailing list