Using [ENTER]

[LaRetta]

I have a basic data entry screen. I always test things on my 70-year-old mother who knows 'nothing' about computers! If she can't mess it up, and can figure it out, then I know all users can easily use it.

Here's the thing ... after she entered data in a field, she hit [ENTER] and it kept wrapping to the next line. Geeeezzzz. Question: When to [TAB] or [ENTER] to move through fields in records, or do I have any control? If at least her cursor didn't move anywhere, she would remember to tab; but I've tried 'locking' the field -- it still spreads. Not only does it look ugly, but it could scare some users!! Any way to stop the wrapping in set fields?

[LiveOak]

To be completely accurate, "Enter" doesn't cause a text wrap in a field, "Return" does. "Enter" actually exits the field (mostly). It's a little complicated. If you have a text field with no value list, tab takes you to the next field, return enters a carriage return into the field, and enter exits the field. If a field is defined with a Pop-up List, tab will exit the field without selection, enter will make the highlighted selection and leave you in the field without the list (a second enter will exit the field), and return will make the highlighter selection and take you to the next field in the tab order.

How to stop wrapping? 1) Don't use text fields, other types don't wrap, 2) Set validation to not accept carriage returns are the only less than satisfactory ideas I can think of. There is no easy way to re-map the keys.

-bd

[LaRetta]

Thanks Brent. I use 'staff code' which is short way to data enter which therapist the line item applies to; I don't know what else I could use but a text field. The field is based upon a lookup, I changed the length to max 3 characters (staff code length), I've tried everything I can to stop it. Nothing works. How could I restrict carriage returns as you suggest? Would it need to be script? Or am I being a bit paranoid? When a user has hit 'return' (it shows as enter on my PC keyboard) several times, and you go back to that field, it expands. Will these carriage returns become part of the data? Thanks for everything you do for us.

[LiveOak]

A good option is to use a "staff code" field, but to also use a value list which not only shows the staff code, but also the staff name (this is easily done if you have a "staff" file to base the list upon). The name isn't entered, just displayed in the pop-up list to assist the user in selecting a code.

-bd