you are making this more difficult than it needs to be by not adapting. Don't understand why so many people want a behaviour that's been around for eons to work some other way.
A control that has an enter key property has 2 options - default (which I presume defaults to your db options setting for record navigation) and New Line. If you want it to do something else, you will have to trap for the Enter key press. Then it introduces the issue of whether or not you put it on every control that needs it, or set the form keypreview property to yes/true so that you can just do it for the whole form. What happens when you start combining Enter with other keys like Alt or Ctrl is a guess for me. If you trap the enter key press, don't be surprised if it slows the form down because the db will have to evaluate every key to see if it's the enter key.
One could just learn that key navigation is Tab, and assimilate! Ok, no more soapbox
Last edited by Micron; 07-19-2019 at 01:32 PM.
Reason: corrected "error key press" to "Enter key press"
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.