Submit Your Suggestions for Vista

Agree but low on our priority list.

Issue:

"N" might be a valid field value.

"+" might also be a valid field value.

I think we need a new approach. Listed below are a few.

Making it so "+" can NEVER BE a valid value by itself in a key field, and use that as the universal "new record" indicator.

Replace the "Empty key field" with a BUTTON that says [N-New].

• Tapping on the 'N-New' button will swap the button to a field.
• If the field is AUTO-INCREMENTING, it will fill in with the new number and highlight it with keyboard focus. This would allow the user to manually change it if they want, or hit TAB to go to the next field.
• If the field is NOT auto-incrementing, keyboard focus will go into the BLANK field, which would allow the user to then type in the value they want.

To make this keyboard friendly, I recommend making it so if the button is highlighted, tapping "N" on the keyboard will fire the button the same as a mouse click.

Using the INSERT KEY

• Remove the usability of "N" and "+" in key fields.
• Use the INSERT KEY instead.
  
  • The key field would POPULATE (for auto-incrementing fields only)
  • The key field would be put in focus.
• Drawback:
  • People with limited (laptop) keyboards. (what percentage of VP users are on laptops?)
  • People are habitual, and removing "N" and "+" might disrupt their workflows.

Any other ideas?