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
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

153 additional answers

Sort by: Newest
Most helpful Newest Oldest
  1. ScottGem 68,840 Reputation points Volunteer Moderator
    2015-12-09T15:36:24+00:00

    Will,

    No I'm not joking. Nor is it brand loyalty. Its a matter of understanding what went wrong and what was needed to fix it and what was done to fix it. 

    You are upset and frustrated by the existence of this bug and the time it took to get it fixed. I understand and empathize with that frustration. But the fact of the matter is this bug was not reported until September. As soon as it was brought to the attention of the Access development team resources were put on it to fix it (your statement that nothing was done for a month is totally false). It took some time to identify the problem, write and test code that would fix the issue. You think it should have taken less time, but unless you have worked on development of a program as large and complex as Office, I doubt if you have the right perspective to understand what needed to be done. 

    The fix is in place and we have heard from people who have applied the fix successfully. I can site several examples of how much Microsoft DOES care about Customer Service, just as I know there are examples of poor Customer Service as well (that MS rep who allegedly said there was no official identification). You are making a generalization based on your own specific experience and that is not being fair. 

    By the way, there are still three weeks left in the fourth quarter so saying it has been broken for the entire fourth quarter is another example of your exaggerations and inaccurate statements. Again I understand your frustration with this issue and that it is leading you to state such inaccuracies. I'm just trying to insert some reason and facts into this issue.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-12-09T14:59:25+00:00

    Are you joking? If anything it's an understatement.

    I honestly don't know why you keep defending Microsoft at this point. Your brand loyalty is absolutely ridiculous. They obviously don't care about customer service at all. We gave them a problem to fix in September (I would argue even earlier) and they did nothing about it for a month. Then we were told (not by them directly mind you) we would have to wait another 2+ months until a patch would be released.

    Here we are 2 months later and it turns out everyone that pays for a 365 subscription still does not have a fix. This is a BASIC FEATURE and it has been broken for the entire fourth quarter of 2015.

    At least now we can revert back to 2013, so now they are realizing their suite is broken, but it sure as **** took them long enough.

    Was this answer helpful?

    0 comments
  3. Anonymous
    2015-12-09T14:12:23+00:00

    The fix for this issue was pushed out on December 9, 2015.

    Was this answer helpful?

    0 comments
  4. ScottGem 68,840 Reputation points Volunteer Moderator
    2015-12-09T12:25:28+00:00

    I understand your frustration but saying that anyone got "shafted" here is really a bit over the top. 

    But thank you for posting that link.

    Was this answer helpful?

    0 comments