Hello,
I have a problem with Access (Version 1904 , build 11601.20204) :

After clicking on hyperlink (file located on local drive or network drive) from Access database , each file is opened in single instance (instead of opening as a new pane in running instance) no matter what type of file it is (cdr, xls, docx, txt). The only exception is pdf which is opened correctly in a single instance.

The most important for us is the cdr (CorelDraw) as it takes about 20 seconds to start each instance and open a file (20 users, each opens 20 - 50 files a day).

We have tested various scenarios:
- opening the files by clicking on them in explorer works normally
- same issue is in Word and Excel
- same results when turning UAC on / off
- tried changing the shell/open command for CorelDraw
- ignore DDE requests in Access option On/off

Only one one PC (which has Admin account only) we have managed to make Access display hyperlink warning "Some documents may contain viruses...." after clicking on the hyperlink and it actually helped - after displaying this prompt the files open in same instance.

This workaround would be acceptable but the problem is that we are unable to replicate this behavior on regular user accounts.

Please help

STOP SELLING THE SAME PROGRAMS EVERY YEAR AND LOCKING MY INFORMATION THAT I NEED TO ACCESS. This is terrible. I remember the time when we purchased WORD, POWERPOINT, ACCESS, EXCEL and the not have to worry that you all will lock up our information because we cannot afford to continually purchase the same programs to get our OWN materials. I am a senior citizen 72 and cannot get to my contacts in ACCESS, can't get to my slides in POWERPOINT that I OWN. And cannot get to my WORD files of the books that I have written over the years. THIS IS COPYRIGHTED MATERIAL THAT I (WE) OWN. NOT 365 Microsoft. YOU ALL DO NOT OWN OUR COPYRIGHTED MATERIAL. STOP THIS. I WORKED 50 YEARS TO GET ONLY $1300.00 A MONTH SOCIAL SECURITY AND NOW CANNOT GET TO MY OWN INFORMATION. THEN FORCE US TO AGREE TO YOUR TERMS WHICH ARE HURTING PEOPLE LIKE MYSELF.

I believe I have hit a new bug in ACCESS.
This conflict shows up when a front end using standard Access SQL connects to a Back-end using SQL Server Syntax (ANSI92).
It results in very strange behavior with Combo-Boxes failing to Auto-Complete and Wildcard Queries not returning results.
Access 2010 is immune! Phew.

It is repeatable and can be reproduced by following the process:
There appears to be a new bug in ACCESS 365 / Click to Run.
It DOES NOT EXHIBIT on Access 2010, but I have not tested with 2013.

Issue: Combo Boxes (drop-downs) fail to Auto-Complete List Items when user is keying Data.
Additionally, some Queries fail to return results.
The Cause:
SQL Server Syntax setting.
To Reproduce:
Create a New Database (Call It TestBE or Similar)
Go to File > Options > Object Designers
Under Query Design find “SQL Server Compatible Syntax (Ansi 92)”
Untick/ Uncheck if selected. Click OK to apply…
Create a new Table tblLinked with an ID (auto-number) field and a Description Field (Short Text)
Populate a few rows of this table with some words
Close the TestBE Database.

Create a new Blank database (Call it TestFE or similar) with Access 365CTR (I’m using Version 1905)
Go to File > Options > Object Designers
Under Query Design find “SQL Server Compatible Syntax (Ansi 92)”
Untick/ Uncheck if selected. Click OK to apply…
Create a small Table tblTEST with an ID (auto-number) field and a Description Field (Short Text)
Populate this table with some random words in the Description.
Create a new Unbound Form (Form1). Add a ComboBox with RowSource set to tblTEST. Set 2 Columns, with Column widths set to 0cm;5cm
Normal Behavior:
Open the form Form1. Type the first letter of a Description in the Combo box. Access will autocomplete the word if matched. Correctly.
The ISSUE:

Now still in the TestFE database; link to the table tblLinked in the TestBE Databases.
Open Form1 and test the Combo again. Functionality is still OK. Clear the Combobox.
Open the linked table tblLinked. It works fine. Close it.
Open Form1 and test the Combo again. Functionality is still OK. Clear the Combobox.
Create a new query on tblLinked. “SELECT * FROM tblLinked” Save this as qryFail.
Open Query qryFail in datasheet view. Looks fine.
Open Form1 and test the Combobox with a single letter . Autocomplete still works.
Clear the Combo box.
Open qryFail again and Click Refresh All from the Home Ribbon.
Now on Form1 test the ComboBox again. Auto-complete Fails!
It will stay failed until the database is closed and reopened.
Any Query’s in the Database using a wildCard Like * will now only return results if using SQL Syntax of Alike %.

In Access 2010 this is not seen!

"Microsoft Graph is the gateway to data and intelligence in Microsoft 365. Microsoft Graph provides a unified programmability model that you can use to take advantage of the tremendous amount of data in Office 365, Enterprise Mobility + Security, and Windows 10.
You can use the Microsoft Graph API to build apps for organizations and consumers that interact with the data of millions of users. With Microsoft Graph, you can connect to a wealth of resources, relationships, and intelligence, all through a single endpoint: https://graph.microsoft.com."

It seems that just about every language except VBA can be used to run this. Access is a database app and it would be great to be able to use it to collect data to feed into, say, Office 365 groups, users and so on.