How can I use the Autokeys macro with keystrokes of the type Shift and key in Access 2016?

Dear All,

I am trying to set up an Autokeys macro in Access 2016 so that it responds to the keystroke Shift and P. I am setting up the submacro name as +P but I am getting a message saying that the key or key combination +P in Autokeys has invalid syntax or is not alowed (although I have seen it in a few books and tutorials). Could someone please advise how can I use Shift+P in Autokeys?

Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Anders Ebro (Microsoft MVP)Microsoft DeveloperCommented:
The below screenshot is an example of a AutoKeys macro that uses Shift-F2 to open a custom zoom form (you can see the zoomform on my blog if interested). I don't know if simply adding the curly brackets around the P would make it work, but worth a try.
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
I cannot get +<AnyKey> to work for Shift. Error message in all cases.
This is somehow broke.
In at least A2003 ... I had a lot of +<SomeKey>

Meanwhile  ^<AnyKey>  works fine for Control

When you try to Save the AutoKeys Macro ... you get this error message:

Anders Ebro (Microsoft MVP)Microsoft DeveloperCommented:
Your screenshot seems to be using regular parenthesis (), not the curly ones {}. Have you tried with the curly ones? (I don't know if they have an official name in english :) )
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Curly brackets solves the problem for +{F2}   but not +{P} ....  same error.  Tried all sorts of combinations for +<SomeRegularKey>
Very ODD.
gklukAuthor Commented:
@Anders, unfortunately it does not; I have already tried that (Shift seems to work fine with Function keys but not with individual ones).
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
In at least A2003 ... I used +<SomeKey> all the time.
Not sure when this got broken ... possibly when the Ribbon was introduced in A2007
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
I just reported this as a bug ... waiting for response.

@gkluk .... what Version  of Access is this ?  (I'm in A2016 CTR

Also confirmed this in A2010 desktop
Shane GroffSoftware Design EngineerCommented:
This is not a bug, and the behavior has been this way since at least Access 2007.  I have not verified with Access 2003.

The help topic for Autokeys is here:
It says "These keyboard shortcuts are a subset of the syntax that is used in the SendKeys statement in Microsoft Visual Basic."
And has a list of examples that do work.

It doesn't explicitly say this, but Shift is support ONLY for function keys.

You could request a change in this area via, and you could give feedback on the documentation page if you would like to see the documentation updated to more explicitly specify what combinations are supported.

Access Engineering

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database Architect / Systems AnalystCommented:
Thanks Shane ...
gklukAuthor Commented:
@DataBaseMX, I am on Access 2016. It would be good if the documentation included some sort of what is allowed, or a history with references on when things got changed and why as it could be quite demanding and time consuming to find when things changed.
@Shane it might be working as expected by the developer, but a little more documentation would have helped I believe.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Access

From novice to tech pro — start learning today.