M
MikeR
Anyone know a group to submit a CDONTS question to?
Thanks, Mike
Thanks, Mike
MikeR said:Anyone know a group to submit a CDONTS question to?
Thanks, Mike
Thanks, Bob.Bob said:I suppose it depends on the context. If you are using it in code being
processed by ASP, then this is the right location.
I know of no group set up specifically for CDONTS questions.
Incidentally, CDONTS is obsolete. See
http://classicasp.aspfaq.com/email/how-do-i-send-e-mail-with-cdo.html
MikeR said:Thanks, Bob.
I have an asp page which e-mails an updated Access db to a couple of
people. One
of them uses Outlook, and it refuses an .mdb file, so I'm renaming
the file to a .txt extension.
Thanks, Bob.
I have an asp page which e-mails an updated Access db to a couple of
people. One of them uses Outlook, and it refuses an .mdb file, so I'm
renaming the file to a .txt extension. As you see, I've switched to CDO
and the problem is the same. Here's a little test page (sorry for the
wrapping):
No I haven't, but I'll check with my hosting company to see if the have aBob said:Have you considered zipping the file instead?
It's not a problem with my Outlook user I just found out today. I use Thunderbird.Daniel said:Have you checked the raw message to see how the attachment is being added? I don't know how to do that.
Outlook will assume that the .txt extension means it's text (and also look
at the MIME headers which likely say it's a text attachment which CDO adds
because the extension is .txt) and so displays it as inline text after a
line in the message body. As Bob has suggested, ZIP the file and send that
as an attachment instead, or get the user to adjust their Outlook settings
to allow mdb files (it should be a simple registry change)
Hi Dan -
Thanks for your response.
It's not a problem with my Outlook user I just found out today. I use
Thunderbird. I did another test run just befor reading the newsgroup, and
the body of the e-mail contains
The original MIME headers for this attachment are:
Content-Type: text/plain;
name="MyDB.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="MyDB.txt"
instead of the original squigglygoop. Does this tell you anything?
As it's only occuring on my machine, I can live with it, but curiosity
compels me to keep trying to find a reason.
Mike
compresses the data (although an MDB doesn't tend to compress well unless
it hasn't been compacted for a while)
<snip>
Zipping is probably the best option - it
Huh? A recently compacted mdb will generally compress to around 25 - 30%
of it's original size. I just tried a few using nothing more than the
Windows XP compression utility. Common file types that don't compress well
are usually those that already use some kind of compression, such as jpg,
gif, pdf.
Dan - Thanks for the explanation. I'll play with it.Daniel said:CDO uses the extension to determine the MIME mapping. By changing the
extension to .txt CDO has no choice but to add the text/plain content type,
because it has no idea that the content of the file is not text. If you gave
it a different extension that was unknown, or a binary data type, it might
help (say .xxx) as that should result in something like
application/octet-stream. Zipping is probably the best option - it
compresses the data (although an MDB doesn't tend to compress well unless it
hasn't been compacted for a while) and will be handled correctly when it's
received without the recipient having to mess around renaming files.
Dan
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.