Button Bugs (1 Viewer)

[Thales750]

Has anyone's buttons images, or text, disappeared. Win 11 Office 365

 

[theDBguy]

Yes, there's a bug in the latest updates and the only solution for now is to roll them back.

 

[Thales750]

Yes, there's a bug in the latest updates and the only solution for now is to roll them back.

Office or Windows?

 

[theDBguy]

Office or Windows?

I believe it's Office.

No Labels Rendering/Displaying on Microsoft Access Command Buttons

A new bug in Microsoft Access appears to make command buttons render without the label text displaying! Here's what we know.

www.devhut.net

 

[GPGeorge]

I've seen reports that this bug is now fixed in Current Channel Preview version 2506 build 18925.20092 released on 23 June.

Note that this bug affected the Current Channel Preview. That's the channel which releases updates first and most frequently. In turn, that means anyone using that channel is not only going to get the newest updates. They'll get bugs first, before they've been identified and fixed.

As a general rule of thumb, production database applications should NOT be deployed in the Current Channel Preview because of that exposure to every bug that appears.

A developer, responsible for maintaining and supporting production databases, probably also needs to have a VM with Current Channel Preview installed so they have a chance to identify bugs before users get them.

Here's a review of Update channels to help you manage your deployments better.

 

[isladogs]

See my article for full details of the bug, workarounds and the fix

Disappearing images and captions on buttons

This article outlines a bug which causes many captions and images to no longer be shown on command buttons in Current Channel (Preview) version 2506.

www.isladogs.co.uk

The bug was in several builds of Current Channel (Preview) version 2506 - affected builds included 18925.20064 / 18925.20076
The bug has been fixed in build 18925.20092

Just to confuse matters, a small number of users on Current Channel have reported being updated to one of those CCP builds whilst on Current Channel

 

[cheekybuddha]

Just to confuse matters, a small number of users on Current Channel have reported being updated to one of those CCP builds whilst on Current Channel

Wow!

If this is the case, then what is the point of the preview channel? If bugs are discovered in preview and still make it in to stable ...

Surely if you're too late to prevent the bug going into stable, then issue a hotfix to stable at the same time as updating preview channel.

MS, why?

 

[isladogs]

That's what I've been trying to find out for the past 48 hours. Its a very odd situation that only appears to affect a very small minority of users
MS are investigating. I was unable to replicate it myself.

 

[cheekybuddha]

I was unable to replicate it myself.

I guess that MS are probably a victim of their megalithic size.

Normally one might dismiss this as an anomaly, or a mistake on the users' part, and it wouldn't be particularly shocking.

What's shocking is that MS' [not so] recent attitude towards testing and quality control makes this completely unsurprising if it turns out to be true.

 

[isladogs]

Sorry but I don't agree with those comments.
There is a lot of misinformation with regard to testing and quality control including with respect to this particular bug.
Somehow, the small minority of users ended up on a build that wasn't released to Current Channel.

 

[KitaYama]

Its a very odd situation that only appears to affect a very small minority of users

I'm not sure if that "a very small minority" is accurate. Me and at least 7 other users that I know, had the same problem and rolled back to the previous version. We simply thought "Again" and didn't bother to ask or report. Everything that worked yesterday, and doesn't work today is the result of an update. So we simply revert to an earlier version without a word.
And I'm sure not everybody reports every bug. So the number of affected users is hard to estimate.

 

[cheekybuddha]

Sorry but I don't agree with those comments.
There is a lot of misinformation with regard to testing and quality control including with respect to this particular bug.
Somehow, the small minority of users ended up on a build that wasn't released to Current Channel.

Perhaps you misunderstood my point.

Hearing of users on current channel experiencing these issues would usually make me think that they have made a mistake and got themselves on the wrong preview channel somehow. And I suspect this is probably the case in these instances

The shocking part is that, due to the long history of MS quality control issues over the last decade, I'm not thinking it unlikely that it's just another MS fuckup.

 

[Silversee]

It is so easy to cast stones...

 

[Thales750]

That's what I've been trying to find out for the past 48 hours. Its a very odd situation that only appears to affect a very small minority of users
MS are investigating. I was unable to replicate it myself.

If you have it, it reveals itself very thoroughly.

 

[isladogs]

I am very aware of what effect the bug has.

You omitted vital information. What is your 365 update channel, YYMM version and build number?