How assign in a form, a function key to a command button.

[twgonder]

Function keys don't get enough credit, or use.
I have a group of command buttons, that I would like to also assign function keys to, to do the same thing.
One function key for each command button.
i.e., help command button code can be invoked by f1. I don't want to globally assign, just for the current form.




How can I do that without duplicating the action code?

[June7]

Something like:

CommandBars.ExecuteMso "Help"

Not all of the function keys have use in Access. Exactly what are you trying to accomplish?

[twgonder]

[QUOTE=June7;498824
Not all of the function keys have use in Access. Exactly what are you trying to accomplish?[/QUOTE]

I'm trying to make my forms "better" for the user, and eliminate inadvertent errors.
And there are people like me that don't like being held hostage to a mouse, when there is a key right there waiting to be pressed.
So I have a row of command buttons that look like this:
(Dang, let's try again. I guess this forum software doesn't like cut and paste of images. Just like it doesn't want to replace selected text while editing.)
And I'd like to know how to downsize the image it attaches after uploading (as if it isn't enough steps to go find and attach instead of just paste and resize.

[twgonder]

And yes I know about "&" in the caption property, I want to press one key, not two.

[Micron]

This is old but still might work and give you what you want

https://bytes.com/topic/access/answe...n-keys-f12-etc

EDIT - forgot to say you'd need to set Key Preview property for form to Yes if you want the form to take precedence. Otherwise I believe the key press will be associated with the control that has focus.

[June7]

How does this row of command buttons eliminate mouse click as well as two-key assignment with &?

[Micron]

I'd say the inference is that if you don't want to click the button with mouse, press the key identified by the button caption.

[twgonder]

@ Micron Thanks, I'll check it out.
See, this is why I like forums, lots of experience and nothing is really new. Someone saw something somewhere, that could take me hours to find even if I knew the correct terminology. BTW, I did search here and on Google before asking--came up empty handed.

[Micron]

BTW, I did search here and on Google before asking

Would be nice if that was wide spread practice but based on a lot of questions I see, it's not. IMO it's worse when I post something with definitive terms and someone asks for an explanation instead of doing a bit of finger exercise.

[twgonder]

How does this row of command buttons eliminate mouse click as well as two-key assignment with &?

So now you want to get into the logic of mini/mainframes and the logical doings of dinosaurs like myself? Instead of accepting the new way of doing things, which is click on a 1mm2 button on the bottom of a form that might save unintended data changes (for example), why do I want to do this?

I am being purposely snarky, but in a fun-loving way. Happy to discuss the design engineering, but not here. Actually more than happy because I would love to learn what objections others might have to my "old-school" way of presentation. Best with a WhatsApp or Skype video call. Teams is still giving me fits. Private message if interested in "being old-school-real in a conversation".

[CJ_London]

which is click on a 1mm2 button on the bottom of a form that might save unintended data changes (for example

so what is to stop someone clicking F2 by mistake?

without duplicating the action code?

Put the code in its own function

[twgonder]

so what is to stop someone clicking F2 by mistake?


Put the code in its own function

But, as someone with ocular and motor disabilities, I'm sensitive to how others have to suffer with minuscule controls.
Are you more likely to make an error on a big-fat command button, or with a 1mm2 control that sits next to three other such controls?

Or make the f-key keystroke transfer to the code for the command button?

[twgonder]

...IMO it's worse when I post something with definitive terms and someone asks for an explanation instead of doing a bit of finger exercise.

It's not spot on point, but let me point out some error I made in syntax one day in this forum, about concatenating strings in VBA, and here is the sample from a M$ manual doing exactly what I did (using + instead of &):

[davegri]

Back to the original topic, here's how you program function keys as alternate to click on form button.

twgon-Fkeys-davegri-v01.zip

Clicking the button or pushing the function key produces the same result.

[Micron]

It is not always wrong to concatenate with +. It just isn't always right or best. In cases, null + A = A whereas null & A = null, which is often not wanted. On my phone so keeping it short.