Can't email PDF files created in Access

[MAdams]

I'm using Access 2007 with Adobe Acrobat 7 Pro. I can print an Access report
to a pdf, but when I try to e-mail it, the recipient gets an "unrecognized
token" message (I can see the report just fine). It does send OK if I "save
as" a pdf, and Access pdf files that I created before today using "print" are
still sending okay. I downloaded a Microsoft update last night for Internet
Explorer 8 for Windows XP. Since the problem just started today, I'm
wondering if there's a connection.

 

[Fred]

Are you using Outlook to sendthe email? Outlook has a built-in defect t hat
it sends attachments in a different file format (.dat) which most other
email software can't open. The problem (and even the .dat extensio) is
hidden from recipients using Outlook, so they think that it went OK. .

The solution is to switch from Outlook to a different a different email
software (like Thunderbird which is free) But the Microsoft work-around for
this problem is to compose/send in plain text format - then the attachments
go out in their real form.

 

[MAdams]

Yes, I am using Outlook, but I've been doing these reports for several months
on pretty much a daily basis, and this is the first time I've had this
problem. I don't really have an option to change the email software since
this is the email my company uses.

 

[Paul Shapiro]

Can Acrobat open the file created by Acrobat 7? It sounds like those files
aren't correctly created. Acrobat 7 is pretty old now so the Office
integration might not be as good as it once was. It certainly came out
before Office 2007. Check that all Adobe updates are applied to the Acrobat
7. You could either use the Office PDF creator, that you said works, or you
might consider upgrading to Acrobat 9.

 

[Fred]

To check if Outlook is a problem:

Try sending it to someone else who is still using Outlook and ask them if it
looks OK. (but still a problem for others) If so, then Outlook is your
problem.

Or send a different (non-pdf) attachment to the same people that have been
having the problem and see if they still have the problem. If so, then
Outlook is your problem.

If so, and if your company is forcing you to still still use Outlook, then
you can use that "compose/send as plain text" workaround when sending
attachments in Outlook.

 

[Mark Andrews]

Why not just use a smtp component to send the email? Just point it at your
exchange server. Most of them are just one dll that you would need and it
gets you away from relying on Outlook. If that is the issue?

Most just require an smtp server name and authentication credientials, and a
few lines of code to send the email.

My two cents,
Mark