Hello Liz
I would advise against modifying this behaviour. It is a per-client (rather than per database) setting, so it will affect all databases opened by that user on that computer. (This is the reason the setting does not travel to other computers when you distribute the front-end.) You could end up annoying people by changing the default setting!
That said, the setting is stored in the following registry key:
HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Access\Settings
The value name is "Move After Enter" and value settings are:
1 - don't move
2 - next field (default)
3 - next record
You can change this programmatically if you wish, but I think a better solution would be to intercept the enter key in the KeyDown event:
If KeyCode = vbKeyReturn Then
KeyCode = 0
End If
Best wishes,
Graham
---In MS_Access_Professionals@yahoogroups.com, <liz_ravenwood@...> wrote:
Pros, I have a db in which if I change the access/options/advanced enter key behavior to "none" the compiled front end does not inherit this property.
How can I programmatically make it so that when the user hits the enter key it doesn't move to the field nor does it move to the next record, nor does it add an "enter" character in the unbound text box?
Respectfully,
Liz Ravenwood
Programmer / Analyst
B/E Aerospace | Super First Class Environments
1851 S Pantano Road | Tucson, Arizona 85710
Office +1.520.239.4808 |
beaerospace.com
Passion to Innovate. Power to Deliver
This email (and all attachments) is for the sole use of the intended recipient(s) and may contain privileged and/or proprietary information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
| Reply via web post | Reply to sender | Reply to group | Start a New Topic | Messages in this topic (2) |
Tidak ada komentar:
Posting Komentar