Forum Discussion
Access VBA performance dramatically slowed since June Update
I have a software product with lots of customers. I am getting a lot of calls about the VBA performance problem. As mentioned here, this was introduced in version 2606 somewhere around Build 20131.20024 and was fixed in Build 20131.20050 (I believe). Current channel preview updates seem to get you up to 20068 and so the problem is fixed. HOWEVER, current channel users are getting version 2606 build 20131.20044 which still has the problem. I have a lot of people have called me in the last several days that have that version and when you try to get updates, it says you are up to date. Microsoft needs to push out the fix for this to the people that they sent version 2606 that are on current channel. Now they will say that people on the current channel should not have version 2606 build 20131.20044 but a lot do. Please fix this!
Hi,
We recently learned from Microsoft, that even the default Current Channel is "subject to experimentation", which means that a part of the systems in this channel get builds which are listed to be in the Preview Channel.
This explains why some people got the buggy build and can't update, as in their channel there's no newer build available. They can a) switch to a different channel or b) wait for a fixed build or better actively choose File - Account - Update Options - Update Now as often as possible, to get a fixed build as soon as Microsoft has released it.
Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK
You can also explicitly download a newer build if it is not getting downloaded through the update now button. Just open a command prompt as administrator and use the following example:
"C:\Program Files\Common Files\microsoft shared\ClickToRun\OfficeC2RClient.exe" /update user updatetoversion=16.0.20131.20090
Hi,
Yes, we have this and other methods how to get a different build in our most popular AFo article. However, this will not help in an update channel where there's no new build available. We also have an article on how to change the channel.
Servus
Karl
****************
Access Forever News DevCon
Access-Entwickler-Konferenz AEK
That does explain a lot about why people in the current channel get some of the updates early like this one with the problem. They did seem to release newer updates now so that people in CC that did get version 2506 will now get a later build that fixes this problem if they just click on the Update Now button. I don't think a lot of people knew about this experimentation policy for the current channel. Transparency is always the best policy.