Computing desk
< July 14	<< Jun \| July \| Aug >>	July 16 >

Welcome to the Wikipedia Computing Reference Desk Archives
The page you are currently viewing is a transcluded archive page. While you can leave answers for any questions shown below, please ask new questions on one of the current reference desk pages.

July 15

Opening Objects in Access by Double-Clicking?

What option do I set so that I can open Access objects (tables, queries, forms, reports) by double-clicking, rather than having to right-click and then select Open? Robert McClenon (talk) 05:33, 15 July 2023 (UTC)[reply]

I forgot to say Windows 11 with the current version of Office 365 or whatever it is called. Robert McClenon (talk) 06:05, 15 July 2023 (UTC)[reply]

You may have encountered a bug which is more than a decade old.

First of all I notice that there is a setting, which back in 2012 was here:

Access Options - CurrentDatabase - Navigation Options - Open Objects With

However, this may not solve the problem, in which case it appears you need to use the workaround of changing your system-wide double-click speed.

The official way to do this on Windows 11 is to open the over-designed and ineffectual new "settings", type in "mouse", click "mouse settings", scroll down to "Additional mouse settings", and this will open the actual mouse control panel where you can actually change useful things such as double-click speed. (Windows has kept its old control panels, but has hidden them behind a thicket of modern-looking but incomplete "settings".)

Or for a quicker route, you can right-click the start button, select "run", and type in "main.cpl".

I'm not sure, but I suspect that moving the slider to "slow" will allow Access to notice double-clicks that it somehow failed to notice before. Card Zero (talk) 11:25, 15 July 2023 (UTC)[reply]

User:Card Zero - Thank you. I navigated to the mouse control panel from the Settings and found the double-click setting, and set it to Slow. That worked. I didn't ask about opening documents in Word by double-clicking them, but that (of course) also solved that related problem. As we know, it wasn't a problem in Access, except that it was affecting Access and other applications. Robert McClenon (talk) 17:12, 16 July 2023 (UTC)[reply]