Query Builder/Design opens Visual Studio Code in Edge

[Jon_H90]

I manage a split database in an Army365 environment, where I'm the sole admin. Recently ( ~2 weeks) ago I noticed when I attempt to open, edit, or create a query, a browser window will automatically open to "https://vscode.dev/". It's not just in my database either, I've tried others within my organization from multiple machines, and the NW Traders 2.0, it occurs regardless.

I have searched the web for any info, searched through the help and everywhere I can think of in Access and other MS Suite applications, nothing points to where it might be a setting from a SW update. I have also called my organization's helpdesk, they didn't know of anything that could possibly lead to it either.

Mind you, Access runs just fine, whether it's opening the browser for the first time or additional tabs, it's a momentary blip of the CPU usage. But it does get to be a bother when I have a browser tab that I want open and another pops up unwarranted, or I'm back and forth between datasheet and design view and have 10 tabs open by the time I'm done editing.

Has anyone noticed this or have any insight on a fix?

EDIT: Added a screenshot of my desktop after occurrence.

[#2]

@Jon_H90 

This is unique problem, and one that is hard to to visualize. It sounds like there is a hyperlink involved. How that could be happening, though, is hard to imagine.

Let's start by clarifying whether this is an autocorrect error:  an Army365 environment.

Is that supposed to be Access 365? 

[#3]

Yes, I apologize. Army365 is just the environment we use (possibly stripped/catered version for DoD, idk exactly), but on Office365. I want to say we transitioned from 2016 to 365 in the spring of last year.

I agree, it has to be a hyperlink embedded somewhere. But that's what I can't seem to find.

[#4]

@Jon_H90 I have no idea what to think. I'm going to ask around. If it were happening when Access itself opens, I'd wonder if there is something in AutoExec, or the events on the initial form that opens. But if NW does it as well, it sounds more like something in Windows rather than Access. 

[#5]

Someone suggests, mostly in jest, that it might be related to the upcoming Monaco editor for SQL queries. Have you discussed this with your IT support?

[#6]

I have not but I will bring it up! A co-worker and I found a machine that is not frequently used and is NOT doing what I described. So, I'm thinking your suggestion of it being windows related is most likely.

If/when I do find the solution, I'll update this post.

[#7]

@Jon_H90  I have the same thing happening to me also with ARMY365. I've been working in access for the past week or two and it wasn't an issue until yesterday. Let me know what you find out.

[#8]

A second corroborating instance is useful. I wonder if the suggestion about an unintended sneak preview of the Monaco SQL Editor for query design has potential.

Maybe it's not just a jest.

[#9]

That's reassuring that it's not just our organization that is affected. I'm still working with my helpdesk and will gladly share what I find.

[#10]

Can you share the Version/Build shown under "About Access" when you do File/Account?

[#11]

Thanks, Shane. We'll be keeping an eye out for possible insights about what could be happening.

@Jon H90 and @hbiemann. The version and build are critical information that Microsoft needs to investigate. Please provide that as soon as you can.

[#12]

@George Hepworth and @Shane Groff: Version 2306 (Build 16529.20154 Click-to-Run)

@hbiemann, is yours the same?

[#13 · Accepted solution]

Yes, 16529.20154 is the current build for Current Channel. I just wanted to make sure that we weren't dealing with an old build. We will resolve this issue for version 2307, which will be released at the end of July.

[#14]

My organization pushed an update to Version 2307 Build 166626.20132. Tested the queries and it's functioning normally again! Thank you!

[#15]

@Jon_H90 

What did you do to resolve this issue? I am experiencing this as well as i am building a database.

[#16]

If you update Office, you should get Version 2307, and should not see the problem. What Version/Build do you currently have?