My favorite Access keyboard commands – part 2

I have a confession to make… I started hacking around in computers with Windows 3.1—never learned how to really use the command line. I know—I have fallen from grace for many of you developers. The mouse has been my friend. I’m trying to change and use keyboard shortcuts more often. Here is a list of keyboard commands I’m trying to use more frequently:

To do this


Cycle between windows in SDI


Open an object from the nav pane in design view


Toggle between panes (nav pane, ribbon, open object)


Expand/collapse the navigation pane


Open a builder or zoom window (when you have focus in a property)


Close an open Window


Expand/Collapse the ribbon

(You can also double click on the active tab)


Set focus to the search box in the nav pane (once it has focus)

ENTER while in the nav pane search box opens the top item in the nav pane in browse.

CTRL+ENTER while in the nav pane search box opens the top item in the nav pane in design.  –Scott (nav pane developer)


Flip an object into design mode

ALT, H, W, D

Open an object in design view with focus in the navigation pane


Refresh a view if the object is in browse view. If a form is in design view it will open in the default view.


F9 – Refreshes the list contents of a combo or recalc expressions for the current record.  Record focus is not changed.

Shift-F9 – Requeries the object.  Record focus back to the top with the current data.  Combo/List box contents may not be refreshed.

F5 should do both or Refresh All. – Shawn (test lead)


Set focus to the search box in record navigation bar


If you have the focus in the record navigation bar search box and press ESC, we’ll take the focus to the form/grid in the selection you had. So you can quickly do CTRL+SHIFT+F, search for something, press ESC, edit it, CTRL+SHIFT+F, etc…   –Marcus (new look developer)


Insert the current date


Insert the current time


Insert the value from the same field in the previous record


Add a new record


In a datasheet, delete the current record


Drop down a combo box when it has focus


Save changes to the current record


Switch between Edit mode (with insertion point displayed) and Navigation mode in a datasheet. When using a form or report, press ESC to leave Navigation mode.


Toggle the Field List

ALT + F8

Open the VBE Immediate window


Open VBE

ALT + F11

Here are a couple help article that provides far more references and

 Sorry about the lack of grid lines or alternate row color–I will try to fix that when I have more time. Many thanks to all the Access team members that chipped in with comments.

BTW – if you haven’t provided feedback about what web data you want in Access on our web service post–please do! This is your chance to provide us feedback about the next version. I can’t promise what will make it into the schedule but your feedback on the topic is extemely helpful.

Updated nav pane shortcut 2/26–Clint.

Comments (6)

  1. ken says:

    Sorry for the OT but it’s important.

    From "Macro improvements of Access 2007"


    "I’m not the security expert on our team and my views don’t represent the views of Microsoft or the Access team. We might even see Suraj (our security expert drop by if he gets a chance).

    I don’t think you will ever see MS changing the security settings to low. There are just too many things that can go wrong. Keep in mind, the security setting effects all Office documents such as Word and Excel. I think most people that get an Excel doc will expect it to be safe. Most of the security hacks these days are social engineering hacks where you trick someone into running your software without realizing it could be dangerous. The security dialog makes people understand the application could run code.

    You don’t get a security dialog when you run Notepad because Notepad won’t ever do anything wrong. You don’t get a security dialog when you run .Net apps because you got it when you installed it.

    Unfortunately, there are lots of bad people that have invested interest in doing harm to others computers. Given the bad things that have happened to Microsoft customers–the company has to take this issue very seriously"


    Clint, we are developers that distribute Runtime .MDE/ADE applications to our customers.

    An Access Runtime application must be (virtually) similar to a compiled .exe or .NET application.

    It’s a big mistake to *force* us to buy the sagekey scripts.

    In my opinion the Access developer team don’t know (or simply it ignores) the needs of Access/VBA developers.

    Microsoft Access-Runtime-edition isn’t an Office application for final users!


  2. Thanks Ken,

    I will pass your feedback along to the Access team. I know they are looking at different deployment options.

  3. AL says:

    Of course, I have to agree with ken 200%.  After some Google or UA investigation, it is trivial for any programmer to inactivate the security warnings, the same way that SageKey does it.  This of course means that any malicious hacker can do the same thing.  So really, what’s the value of this, other than annoying people.  

    IOW, the security warnings do nothing to enhance security, but are a great embarrassment for developers and a great annoyance to end-users.  

    At the same time, there is not even a peep in the help files about the dangers of SQL injection to delete all of my data, and not a peep about the dangers of using SQL Server security to apply permissions that can then be used outside of the Access application.  When will Access support application roles, which provide much better security and performance?  (Some time ago, you or Eric said you would try to look into it, but we have not heard back.)

    Please try to understand that this current approach to "security" simply does not work in practice.  I suggest that the next blog post be used to solicit users’ concerns and suggestions about Access security issues.  You can add a poll that asks developers: "Who likes the current "security model."

    Having said all that, I want to thank you gain for making this blog and keeping open the lines of communication.  I, for one, really appreciate it!  

  4. Please keep in mind, a malicious hacker can’t modify the low security settings without tricking you into running code on the system. The only way the SageKey system might be allowed to do it is because someone trusts the person installing the code.

    I understand there are some frustrations with the current security model. Trusted Locations does help in many scenarios but not all. I will pass along the feedback to the people that manage those decisions.

  5. I did more research on this topic–I’m not that connected to the runtime these days. It turns out–I gave you some wrong information (sorry about that). When you create the runtime MSI the runtime will add a trusted folder reg key for your data folder. This means, we will run your application without security prompts without lowering all of your Office security settings. T


  6. AL says:

    🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂 🙂

    (Yes, Thank you!)