In addition to the other comments here, you might actually be trying to
prevent record movement, and not actually kill to those keystrokes.
If you want the table key to cycle round and round in the same form, then in
the form other tab, set the forms cycle property to current record. Then,
when you get to the last field on the form, the tab key (or Enter key) will
jump to the top of the screen.
It is a little harsh and goes against the windows standard UI to kill the
tab key, when that has been the defacto standard FOR AT LEAST 10 YEARS.
It is a sure sign of some terrible software design if the tab key has to be
disabled. I cannot imagine the frustration you going to place on your users
when they start hitting tab key, and the cursor does not advance? Further,
for things like memo fields etc, you can set the Enter key to start a new
line, and thus the users really do need the tab key to go the next field. I
would *really* think hard about removing one of the most common keys for
navigation in a form. Your users will hate you for this....
