What occurs when it stops working is CDO thinks it sent the message but the message actually sits in

C:\Inetpub\mailroot\Queue

and never leaves. I have verified the permissions for the mailroot directories and the configuration. Basically, if the user has a default email client configured in Outlook Express, then it will work. If anything changes and the account setup in Outlook Express is no longer valid, then CDO won't work either. You can manually set the smtp server to a valid smtp server using CDO if you know what it is. That will work everytime in my testing, however, I will not know what the smtp server is at the client's site and some ISPs are not too happy about installing your own smtp server. We do not require our users to configure the smtp server on their systems and do not want to go that route. It simply seems to leave too much at risk to be guaranteed reliable so I am researching other alternatives. I like the idea of the shellexecute option because it will simply launches the default email client and we can require our users have an email client without requiring it be any specific one. However, since it doesn't allow for sending attachments, that is a drawback. I have tested using MSMAPI successfully but I have also read numerous messages on VFP forums where it may fail also so I haven't found anything that is guaranteed reliable yet.

>Hi Tracy,
>
>Your comment, "Since CDO has stopped working intermittently..." is of particular interest to me, since I am about to use CDO to send import emails to our cilent. Could you please provide more information about the problem? Is it that it does not work now but will work after 10 minutes? I believe that when it does not work, at leaset send() will return .F. (so that I know that the mail did not go through and I can try later.) Any comments on CDO's reliability?
>
>Thanks.