E-Mail button disabled on Print Preview

kevlray

Registered User.
Local time
Today, 15:07
Joined
Apr 5, 2010
Messages
1,045
We have a user that wishes to e-mail from the Print Preview window. But for some reason the e-mail is disabled. I opened a different database ( I do not have access to their database) and opened Print Preview window and the e-mail button is not disabled for me.


What should I be checking on their database/Access installation to get e-mail to work from Print Preview.


Not sure on the exact version of Access, but it is 2007+.


Thanks in advance.
 
Is the PrintPreview tab on ribbon showing? Then the E-Mail button is greyed?

This happens with all reports?

Sorry, cannot replicate issue.
 
The Print Preview tab on the ribbon is showing (all I have is a screen shot). And the e-mail button is greyed out. They currently they only have the one report (user created DB).
 
I'd never really thought about this before.
However, just checked the Email button in the Print Preview ribbon with a couple of my own apps:
a) Access 2016 - button enabled
b) Access 2010 - button disabled (tested on two PCs)

Its never been an issue for me using 2010.
I've always saved the report as a PDF then attached it to the email.
Whereas, in 2016 where the Email button is enabled, you've still got to choose an attachment format such as PDF.

So is that a satisfactory work round for you?
 
Hi. Are you using a custom ribbon? If not, maybe you could try one.
 
I use Access 2010 and the E-mail button is available, not greyed out.
 
Just had a thought on this lovely snowy morning

It may be the button only works if you have the same version of Outlook installed.
On the first PC I tested in A2010, I also have Office 365 so Outlook is a newer version.
The second (tablet) PC doesn't have Outlook. It uses Windows Mail to save disk space.

I do have a VM with Office 2010 only. Later I'll check if its enabled there.
However the work-round I mentioned works perfectly for me.
 
Works for me on 2007.
In fact I wish I knew of this, as I was printing to pdf and emailing.:banghead:
 
Just confirmed my hunch from post #7 by checking on an Office 2010 VM..
The Email button is DISABLED if Outlook isn't installed or if its from a different version of Office to Access.
 
Years back I found that this issue is not necessarily linked to Outlook (version) but the need for a MAPI compliant email client to be set as the default.

Cheers,
Vlad
 
Years back I found that this issue is not necessarily linked to Outlook (version) but the need for a MAPI compliant email client to be set as the default.

Possibly in certain cases, but that wouldn't explain the differences I got on the machines used for testing here.

Anyway, I still feel its a minor issue:
EITHER click EMail then create a PDF or RTF or whatever (if button enabled)
OR save report to PDF or RTF then attachment to email (if button disabled)
Both amount to the same thing but from different directions
 
I've Windows 8, MS-Access 2010, using Thunderbird for E-mail.
By me, the E-Mail button is enabled.
 
FYI: Found out the user is using Access 2016. There are no customization's to ribbon. In general we use Novell Groupwise for our e-mail (interesting it works for me and I do not have Outlook, but have Access 2013).
 
Is GroupWise set as the default email client for that user?
 
I would think so. GroupWise the standard e-mail for the organization. Checked to see if GroupWise is the default e-mail on my computer and it is not (and the e-mail button works on my computer).
 
What email client opens on yours if you try to email a report?
 
GroupWise.



Just found out that the issue is Windows 10 related. The user just got a new computer with Windows 10 and now the button is greyed out. Also I checked to see that GroupWise was a default program.
 
I do not believe those links are useful in my case. I did come across an discussion where a particular build of Access 2016 (1806) that has an issue with Windows 10. I do not know what build the user is on (and tightly controlled by our IT department). Thus I can only hope that the issue will be resolved in another build.
 

Users who are viewing this thread

Back
Top Bottom