Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations sizbut on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot send email

Status
Not open for further replies.

tekkyun

Technical User
Oct 23, 2003
122
GB
I have a form with command button which uses DoCmd.SendObject method to generate e-mail.
This works great on my PC and some others but on 1 particular pc it consistently generates a microsoft access message "Cannot send email because of the reasons stated in the previous alert".
This particular pc is running exactly the same versions of access (access 2000 with service pack 3) and outlook 2003 as mine.
Another PC will generate and send the email ok but it ignores the editmessage flag to bring the email up on screen before sending it.

Has anyone got any ideas how to make these PC's behave like mine?
 
Hi tekkyun

Have you tried checking the options setup in each copy of Outlook.

As an example, if one user's Outlook is set up so that he needs to supply a password before mail will be sent, that could interfere with your code.

If there are any options set up differently from your PC, try changing them.

Just a thought - no scientific basis for my comments.

Regards

Mac
 
Thanks for your comment Mac. I will check setup for differences.
Since my original post, I have done some further tests and have isolated the problem to PC's running Windows XP.
Last week I was testing using one of the XP machines and it gave errors consistently, but this week the problem has disappeared! Our IT dept have assured me that no software changes were introduced over the weekend so I will check other PC's.
Out of interest, I did find reference to the problem in
Microsoft article 260819 which confirms that SendObject method is a problem in Access 2000 but article seems a bit vague about causes.

Regards,
Mike
 
Another possibility is that you have encountered the Outlook Object Model guard on the later OS PC's.

Thread181-1124764 might be relevant

Regards

MD
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top