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

The problem is not that the bug exists, it's that Microsoft is not giving us the option to go back to 2013 when things actually worked.

Saying this is not an issue to most people so it's not an issue is not acceptable. Just because you personally don't use pictures in your reports does not mean no one else does. Access is one of, if not the only, office program that is used almost solely by companies, not by individuals. When things like this break businesses have to take time out of their day to fix the issue (or not) which costs money. 

I am not impressed by Microsoft's response time to this at all. I doubt I will be renewing my Office 365 subscription this year and I will advise others to do the same if at all possible.

That's pretty bad, can't believe a bug that was spotted in beta is now even apparent in release, let alone taking 2-3 months to fix it.

Do you have any proof that this was discovered in beta? Yes we have, at least 1 person here, claiming to have spotted it in beta, but there is no proof it was reported. My information was that it was not reported during beta. 

What I think is "pretty bad" is people railing against Microsoft for relatively minor bugs. Office is an immense conglomeration of millions of lines of code that is developed by different teams with different focuses. That's why MS does public betas to try and catch as many such bugs as possible. It is totally unrealistic to expect software as complex as Office to be totally bug free on first release. The hope is that bugs will be relatively minor, affecting narrowly defined combinations of circumstances. This is, in my opinion, the circumstances we are dealing with here. 

I can understand and appreciate the ire, if you have to do something within this specific set of circumstance and it doesn't work. But, before you start heaping derogatory comments, you should step back and look at the bigger picture here. That's what I'm trying to bring to this discussion, a more global perspective. 

"it's prompted us to look into other software / systems that will replace Access, OneDrive and, eventually, MS 365 products completely." That is your prerogative, but I doubt if a) you will find a product that offers the depth and breadth of features that Office does and b) you will find a product that does not have the same issues with bugs.

That's pretty bad, can't believe a bug that was spotted in beta is now even apparent in release, let alone taking 2-3 months to fix it.

What's not a deal breaker for some is a real deal breaker for others!

I will say this, along with the time scale it's taken to fix OneDrive For Business to be a useable product (for anyone that isn't storing masses of data, but do have 10000's of small files), it's prompted us to look into other software / systems that will replace Access, OneDrive and, eventually, MS 365 products completely.

Still, no point in continuing to moan about it, MS will fix it in their own time, as per usual.

Rod,

I didn't say its not an issue. It certainly is an issue. I just don't think it is a deal breaker. And your analogy doesn't work for me. Its more like a regular car with a broken real wiper. It still works and it still does mostly the same thing, but one, fairly small, part doesn't work. I'm also a long time IT person. Been working in IT for more than 30 years. And it depends on the flaw and its impact. Office is a very complex application and there are many parts that have to interact. 

I'll give an example. My company uses a product from the one of the top 5 ERP software companies. We encountered a bug about 3 months ago. We went through several weeks of testing to get the bug acknowledged and another 2 months to get a fix published. So this is not at all unusual. 

Home grown production systems are not the same as complex commercial software. 

Symdi said; " I noticed this problem while in beta.."

Did you report it? If you did not report it you really can't complain.