We are well aware of this issue and are working with the Windows team on resolving the problem.
This has just started to be an issue with one of my clients. One of those who had the 3340 error 2 weeks ago.
Seriously... is there any effort being made to address this?
In the past a new release had three years worth of changes and it was difficult to communitate them all.
Now the we have a subscription model where new features can be released at any time rather than waiting for a major release,
The Access Development Team should now have a site where you can view release notes, install the new version and Explicitly turn on new features after having read and understood their effect.
My two cents - ACCDBs should be more closely aligned with SS.
For example, When upsizing data from Access to SS you often find all sorts of rubbish data that Access allows but SS won't.
Applying the same rules and more closely aligning data types would make the migration easier. And this includes preventing bad field naming in Access as well as bad data.
What kinda like RDP?
Well you can do this now with an Azure VM running windows server but I've yet to figure out how to offer anonymous access.
Currently, If you are using another control as a parameter in the Rowsource,
and you are displaying an unbound column (ie Column(0) is an ID and the bound column with its width set to zero, while displaying a text value in Column(1))
then the combo box will not display values in other rows that are not included in the rowsource as defined by the parameter on the current row.
The current workaround is to denomalise, or use Dlookup to display the contents of column(1) in a text box. Which is a bit messy.
Users often have a specific printer not available to the developer, for example a label printer, and having this selection overwritten with each new version requires considerable effort to correct.
Allen Browne's solution works but it's not easy to implement.
In fact the SQL view for queries requires a lot of work. Currently doesn't even have a find and replace! But yes formatting would be great.