Exporting via Email from Access 2010

[clrockwell15]

I did have the capability of exporting my access extracts from access 2010 by running the extract and clicking on "External Data" and click on "Export", and click on the "Email" icon. Had to reload MS Office 2010 and MS Access 2010. Since that, the "Email" icon under "Export" is greyed out. Don't know how to get it back.

[June7]

Did you install Office Service Pack updates as well?

[isladogs]

It may not help directly but the Export EMail option is also disabled for me using Access 2010 in Windows 10.
I also found that that Email does not appear in the context menu when you right click on an object in A2010

As a test, I tried adding the Outlook VBA library but this had no effect on the above

I then tested using Access 2010 running in Windows 7.
The Export ... Email ribbon option is enabled & working ... but its still not listed in context menu

However, the command is available from the External Data ribbon in Access 2016 with Windows 10 (but is still missing from the context menu)

So it looks like a Windows 10 / Access 2010 bug. I have reported it via Windows feedback hub & suggest others do the same to increase the chances of a response

[June7]

I have Windows 10 Home (ver 1803 OS build 17134.112) and Access 2010 (ver 14.0.7208.5000, 32-bit). The email icon is definitely available and works. Not in menu. Doesn't matter if library is/is not selected.

[isladogs]

@June7
How VERY strange.
I have exactly the same Access version as you and Win10 Pro v1709 OS build 1622.431

As you have Win10 v1803, please could you do me a favour and test my Get Current Geolocation sample database available from https://www.access-programmers.co.uk...d.php?t=299932
A bug in that version stopped the IE geolocation service working.
MS supposedly fixed it within 3 weeks of me reporting it in May but I still have 2 PCs where the fix didn't work (so I've reverted to v1709)

[June7]

Got an API key, entered it to db. Tried your GetLocation procedure and get "geolocation service failed - this is a known bug in Windows 10 Version 1803". My last update was June 11, 2018.

[isladogs]

Thanks for trying. If you look at post 2 in that thread, MS released a fix on 12 June but that updates v1803 to build 17134.112 which is what you have.
So their fix didn't work for you either.
So far I've only found two workstations where the fix worked.
Whilst I wait for them to fix it properly, I've tried using vba to open Edge instead to run the same code.
That's surprisingly difficult due to Edge being a 'modern' UWP app.
So I reverted to v1709