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-09T13:15:13+00:00

    Feel free to disagree. But while there have been no significant changes in desktop Access, Access is still a PART of Office. This issue could have been caused by a change in the Office shell that adversely affected Access.

    I was commenting more on your statement that it isn't the user's job to test. Every major software product goes through user testing. its the only way to catch some bugs.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2015-10-09T13:09:58+00:00

    Tom,

    Not to my knowledge.

    RichardGVAZ

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2015-10-09T12:15:59+00:00

    I disagree.

    This was presumably a long project (maybe 3 years?).

    As a typical user I haven't seen any significant changes between the versions to indicate much in the way of changes under the covers.

    I would expect that a feature that was working properly should not suddenly cease to work.

    In my experience a normal project should include stringent change control procedures with strict documentation covering the proposed changes, the effects on the existing system and the expected outcome, along with the documented test results (including failures and re-runs) and whether the expected outcome was eventually achieved.

    I can't believe this was the case for the Access project.

    Was this answer helpful?

    0 comments No comments
  4. ScottGem 68,840 Reputation points Volunteer Moderator
    2015-10-09T11:33:18+00:00

    No.

    Surely it's Microsoft's job to properly test their software, not the users.

    Have you ever deployed an Access application only to have users discover a bug because they did something you didn't expect them to do? That is why company's beta test software, because users will do thinks unexpected. While this is a serious bug, its also a fairly obscure feature with a very specific set of circumstances and I can understand it being missed.

    It should be fixed in the next cycle of updates, hopefully sometime in October. But to expect a program as complex as Access or Office to be released totally bug free, is unreasonable.

    Was this answer helpful?

    0 comments No comments