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

Message truncated at 255 characters in auto emails through access using outlook

P: 1
I'm sorry to resurrect an old topic ( Send Email Through Query ) but I am using the code you posted here to send auto emails through access using outlook. Everything works beautifully except the message in the email is truncated to 255 characters in the resulting email even though the EmailBody is set as type memo and the full message displays in the tblCustomers and the query. I also tried exporting the EmailBody field from the query to a text file and it is truncated there as well...

I have been searching for a resolution to this for a couple days now and would appreciate any help available. Here is the test database I was using: http://goo.gl/8U0Ou6

Thanks!
Dec 4 '13 #1
Share this Question
Share on Google+
1 Reply


zmbd
Expert Mod 5K+
P: 5,285
sirhacksalot:

-You are always welcome to start a new thread containing a reference to an older thread for context.

- 255 truncation with memo fields using the sendobject method is a known issue... well... feature in that 255 is the limit imposed by MS by them for the body message text using the docmd.sendobject()
I've found that the only reliable solution is to use either Outlook automation or CDO (IMHO). Which path to take is up to you. You will find some of the automation code and usage covered in one of our insights articles: http://bytes.com/topic/access/insigh...ion-automation

-Your file is not available for me to look at due to it being a thirdparty file storage site and my IT-Dept prohibits me from downloading any such file.

Also, please understand, many of us cannot or will not d/l un-requested attachments. In my case, such d/l are prohibited by my ITSec staff. For many others, it is part of "safe computing/best practices" not to d/l such files. A practical example as to why can be found here http://bytes.com/topic/access/answer...l-ms-products. this unfourtunate Member opened a file from a trusted source and is now haveing all sorts of issues!
Dec 4 '13 #2

Post your reply

Sign in to post your reply or Sign up for a free account.