And the hits just keep on comin'...

I use a reference to the MS Scripting Runtime in almost all of my applications. I am doomed:(
Ditto. I have been slowly weaning myself off of Scripting and VBScript - converting them to PowerShell - for sometime. Looks like I may have to speed up the process.
 
I dunno, but I wonder if this is somehow related to MS's move away from COM as well. The evil white-lab coat wearing scientists at MS are up to no good...
 
Doesn't this affect the File System Object? I thought it was also in the Windows Scripting library. Someone needs to (as the article says) "roll a hand grenade" into Microsoft's product managers.
 
Yes, it impacts Dictionaries and the FSO, among others I think.

We work so hard to combat the "Access is dying" myth and then MS sort of contributes to the narrative by shopping off bits and pieces.
 
I wonder why these forums don't have some initiative to invite all users to send petitions to MS. Look at how much development is dedicated to Excel.

I discussed something similar in another forum, the limitations of Access probably relate to its clientele not asking for the features. But there seems to be a strong belief in these communities that its code and architecture is some sort of unmovable entity, I really don't understand why. MS has the resources to make Access the best choice, to rewrite stuff, incorporate what is needed, but how are they going to make such a decision when nobody is asking for it? If you were in charge of making Access profitable for MS, would you implement stuff nobody is asking for? Probably not.

So, why not invite the thousands of users who read this forum to directly ask for the changes, the continued development and overall improvement of the app?
 
Can I stress that that although we know VBScript is being phased out, the rest is currently just speculation.

Suggest someone posts a comment about the possible implications via the Feedback Portal and then posts a link here so that others can upvote
 
I think the speculation is probably quite accurate, but you are right, it is still early days.
 
It may well be accurate but both Mike Wolfe and Jan Karel Pieterse did say they had no evidence that FSO, RegEx etc would be affected.
Somehow that got 'lost' in the overall thrust of the article.

Perhaps relevant is that fact that IE has been deprecated but the IE browser control will be available until at least 2029, by which time nobody will care when its deprecated as well.

The feedback portal link is still available in Access. Click the Help tab in the ribbon then Feedback and choose the best option.
 
Yes. 😁
I checked before replying just in case it has been moved/removed.

1698957757670.png



For info, I've also asked the Access team for clarification on this issue.
When I get an answer, I will respond in this thread providing doing so doesn't break NDA (non disclosure agreement)
 
We work so hard to combat the "Access is dying" myth and then MS sort of contributes to the narrative by shopping off bits and pieces.
Do you ever wonder whether MS are trying to tell you something, George! :oops:
 
LOL!
Its been there for several years but there's also a Help Improve Office button on the menu bar which does the same thing

1699027563948.png
 
What version is that?
I have A365 version 2311 and mine looks like this:

1699033046921.png


The QAT icons in your screenshot are inactive but should change appearance when activated.
Note the difference between e.g. the Undo & Redo icons in my screenshot

As a further variation, when in the Backstage view, clicking the Feedback item below Account opens the same Feedback panel as in post #16.
However, when the backstage is open clicking the menu bar icon that I highlighted in post #19 opens this form instead.

1699033501690.png
 

Users who are viewing this thread

Back
Top Bottom