Access 2016 Dragging Queries into Macros crashes Access
When creating macros in Access 2016 if you drag a query into the macro into white space it works fine and adds the query however if you happen to drag it over another query access with crash, no errors or anything just crash out.
I recreated the issue in our environment with a blank database to remove any other variables that our production databases may inject to the issue and I get the same behavior.
I've also tested on a fresh windows install with Office 2016 installed from the office 365 portal.
Users on the access for developers forums were able to recreate the issue as well.
Thanks,
Eric

Thanks for posting this behavior here!
We are looking into it.
Thanks,
Michal [Microsoft]
6 comments
-
Robert commented
Something changed mid-2020 with Office 365 causing significant performance issues in Access. Normal nightly updates that were taking 8 hours suddenly took 2.5x longer. I had IT uninstall 365 and replace with stand-alone version of Office 2016. That fixed the performance issue, but now I have this crazy drag-drop-crash issue in Access. Queries can still be added to macros through the drop-down, but it removes a useful productivity feature. I'm confounded by how a product (O365, 2016, doesn't matter) can be this buggy given its age and supported by a company as well-endowed as Microsoft.
-
edwards142 commented
Well I have encountered through this MS Access crashing issue each time I tries to open my report in Access. So, the solution which I have tried to resolve it out, I can share with you all. Try them out and easily get rid of this MS Access crashing issue whether it is occurred in any of the MS Access version 2007/2010/2013/2016.
I found this helpful post, after a searching a lot for the fixes when I too stuck with such an issue. ….so good luck and share your experience after trying.
source:
http://www.accessrepairnrecovery.com/blog/fix-ms-access-keep-crashing-issue -
Anonymous commented
Any update on this?
-
Tyler Pickering commented
Has there been an update to this issue?
-
matt commented
I have this exact same issue.
Incredibly frustrating.
-
Lawrence Welsby commented
Having the exact same issue.