Pictures not showing in printed versions of reports (or in print previews)

Anonymous
2015-09-28T16:28:54+00:00

Hi all,

I have an access acce that i run on two different machines, one of which is in windows 10 /Office 2016, the other one is in Windows 10 / Office 2010. My Acces prints out perfectly on the 2010 version of Access and no image is coming our on the 2016 version on Office (the same Accde was printing perfectly as i had Access 2013 before the weekend) now no image is coming out on the print.

If I look on screen at the report, pictures are there, as soon as I get onto the print preview, images are gone !

This is probably a new feature of access 2016 that I am not aware of !

Can anybody help me ?

Thanks in advance

Marc

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments
Answer accepted by question author
ScottGem 68,840 Reputation points Volunteer Moderator
2015-11-09T18:23:13+00:00

Patrick, I fully understand the affect this has had. And I couldn't agree more that a way of going back should have been made available. But it doesn't really matter how specific the issue is, a fix needed to be found, tested and then implemented within the rollout cycle. As I understand it a potential fix was identified late in October. And the testing made it miss the November cycle. Hence the December release.

Was this answer helpful?

1 person found this answer helpful.
0 comments No comments

153 additional answers

Sort by: Newest
  1. ScottGem 68,840 Reputation points Volunteer Moderator
    2015-10-20T18:17:47+00:00

    4 months to fix an issue in a production system would land me into a lot of trouble.  

    I'm not sure where you are getting 4 months from. The issue first came to light near the end of September. Assuming the current timetable, it should be fixed by mid December. So that's less than 3 months. While I would have liked to see a quicker release of a fix, this was not a bug that rendered the program useless. So I don't see the time frame as that much of an issue.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-10-20T18:01:43+00:00

    I just installed 2016 and ran into this issue.  Reading through this discussion and now seeing the issue won't be fixed until at least the December updates is quite disturbing.  I'm a long time IT person and 4 months to fix an issue in a production system would land me into a lot of trouble.  Hopefully I can find an older version somewhere as I need to publish this report long before December.

    Was this answer helpful?

    0 comments No comments
  3. ScottGem 68,840 Reputation points Volunteer Moderator
    2015-10-20T16:34:26+00:00

    The last we have been told was a fix was being tested and should appear with the December updates.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2015-10-20T16:02:12+00:00

    I am also having this issue. Is there any update from Microsoft on a time table for a fix?

    Was this answer helpful?

    0 comments No comments