Solved Unable to access sql view of queries

[KitaYama]

When I open one of my Accdb FEs, and open a query in design view, the context menu doesn't show "Sql View".
If I shift double click the database, the "Sql View" is back again.

I've removed all codes from Autoexec, OnLoad and OnOpen events of the first form that opens, still the moment that the database opens, design view of queries lack the "Sql View" context menu.

The database can't be corrupted. All queries, forms, tables, reports and modules are doing their job without any problem.

Is there any option somewhere that hides the sql view of queries?

Thanks.

 

[KitaYama]

Found the problem.
Seems that when "Allow Full Menu" in options is not ticked, "sql View" doesn't show in the context menu.

 

[isladogs]

EDITED:
Just checked this as it didn't seem right to me.

Its still visible in the query context menu from the navigation pane after disabling full menus
However, (after rechecking), I agree SQLView in missing from the context menu when a query is open in design view or datasheet view.

Suggest you try deleting the following registry key (after making a backup):
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Access\Settings\CommandBars
Doing this will allow Access to rebuild all the context menus as they are needed.
Does that fix the issue for you? It didn't for me.

EDIT 2:
This goes all the way back to at least A2010. I think its a bug rather than a deliberate feature

 

[KitaYama]

EDITED:
Just checked this as it didn't seem right to me.

Its still visible in the query context menu from the navigation pane after disabling full menus
However, (after rechecking), I agree SQLView in missing from the context menu when a query is open in design view or datasheet view.

Suggest you try deleting the following registry key (after making a backup):
HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Access\Settings\CommandBars
Doing this will allow Access to rebuild all the context menus as they are needed.
Does that fix the issue for you? It didn't for me.

EDIT 2:
This goes all the way back to at least A2010. I think its a bug rather than a deliberate feature

I'm at home. Tomorrow I'll try your registry workaround and will report back.

thanks.

 

[isladogs]

I very much doubt it will work as it didn't for me. However, its worth a try.
I now know this has been an issue since A2010. It was OK in both A2003 & A2007
I will report it to the Access team

 

[KitaYama]

Its still visible in the query context menu from the navigation pane after disabling full menus

I don't have "Sql View" in my context menu from navigation pane, no matter the mentioned option is ticked or not.
(Microsoft 365)

 

[isladogs]

That was added to Access 365 plus 2016/2019/2021 in version 2311.
Assuming that applies to you, it may be blocked by a custom command bar setting.
The fix is to delete the command bar keys as mentioned in post #3
See my article:

Open Queries Directly in SQL View

This article describes a new feature which for the first time allows you to open any query directly to SQL View from the navigation pane, VBA code or a macro. This will be a huge time saver for developers who prefer to use SQL view rather than the query build editor (QBE)

www.isladogs.co.uk

 

[KitaYama]

That was added to Access 365 plus 2016/2019/2021 in version 2311.

I haven't updated since 2304.
I really hate the height of title bar in recent updates. It takes too much space for no special reason and I couldn't find a way to change its height.

Thanks for reporting this to MS.

 

[isladogs]

How / why have you managed to stay on v2304?
If/when they do fix this you won't get any benefit unless you do update!
I don't like the title bar height either but not enough to turn off all updates

Please can you state the version number, build and update channel when you do report problems
e.g. Access 365 Version 2405 Build 17628.20006 32-bit Beta Channel

That info may make a significant difference to the advice given

 

[KitaYama]

How / why have you managed to stay on v2304?

Simply turned off the auto update option.

Please can you state the version number, build and update channel when you do report problems
e.g. Access 365 Version 2405 Build 17628.20006 32-bit Beta Channel

Is this enough?

 

[isladogs]

The build info on that page is often incorrect. You should use the info next to About Access and add the bitness. No need this time but please do so when you next have a problem

 

[epiek]

Found the problem.
Seems that when "Allow Full Menu" in options is not ticked, "sql View" doesn't show in the context menu.

Hi All
I have spent a lot of time trying to figure out why the MS Access SQL editor window was not showing any results.

I was working on another server's version of Access.

The option Enable Monaco SQL editor was ticked, untder Access Options, Current Database. When I unticked that, I could see the SQL coding!

Jsut thougt I would help others!

 

[isladogs]

Not sure what this means...

I was working on another server's version of Access.

The Monaco SQL Editor is very slow to load with the window appearing blank for 2-3 seconds until the SQL appears.
This is a known issue and is due to the way that it integrates with the Edge browser control. It is hoped that the code used will be further optimised.

In fact, it one of many issues that have been reported to the Access team and which are currently being investigated / fixed.
See my blog article which is being updated regularly:

NEW - Monaco SQL Editor

The new Monaco Editor is the fully featured SQL editor from Visual Studio Code with standard IDE functionality such as syntax highlighting, Intellisense and autocomplete. The most obvious change is the use of color for different sections of the query SQL.

www.isladogs.co.uk