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: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2015-11-06T14:54:14+00:00

    I'm not sure why you aren't seeing the image size property (it should be the fourth option down), but you can set it manually using VBA.

    Under the report "On Load" event procedure use the following code:

    Me.WhateverYourImageNameIs.SizeMode = acOLESizeStretch

    Note that the image name is not the name of the file, but rather the name that Access (or you) assigns to it. The default will be "image26" or something to that effect.

    Was this answer helpful?

    0 comments
  2. Anonymous
    2015-11-06T14:22:44+00:00

    Dear Scott and Tom - 

    Thank you for the Link to the fix: 

    http://blog.fmsinc.com/microsoft-access-2016-and-invisible-picture-images/

    I tried to follow the directions but my image is still invisible and on the property sheet for my image I no longer see the option to change the image from zoom to stretch or clip.  The property sheet seems to have only truncated options.  Is there another setting I am missing?

    Thanks!

    Was this answer helpful?

    0 comments
  3. ScottGem 68,840 Reputation points Volunteer Moderator
    2015-11-06T14:16:54+00:00

    Patrick,

    First, I fully empathize with you on the frustration and issues this has caused you. But like Tom said, I do not work for Microsoft. MVPs are independent individuals who volunteer their time and expertise to help others use Microsoft products. While our MVP status gives us contact with the product team we have limited influence. Because of that contact, we have been able to report this bug and have been notified of the progress of a fix. We have, on our own (not at the request or instruction of MS), passed that information to the community here.  If you looked at the post I made before yours, a fix is planned for December. I also, in a previous reply, posted a link to a work around from FMS founder Luke Chung (a fellow MVP).

    The product team was made fully aware of the extent of the issue once it was reported. The problem originated, not in Access but in changes made to the overall Office suite that affected this part of Access. As you said, you are not a software engineer, so while you may think this should have been an easy thing to fix, I can tell you that its not as simple as you might think to find the code involved, work out a fix, test it and set up deploying it. And remember this had to be done in cooperation with the team that works on the code that caused the problem.

    Was this answer helpful?

    0 comments
  4. Tom van Stiphout 40,216 Reputation points MVP Volunteer Moderator
    2015-11-06T06:05:31+00:00

    > couldn't one of your HIGHLY paid ENGINEERS

    I understand your frustration, and as we have said before a fix is still on track for the December update, but I want you to understand that neither Scott nor any other MVP is working for MSFT. We are unpaid Access enthusiasts trying to help the community. Show him some respect.

    Thanks,

    -Tom.

    Was this answer helpful?

    0 comments