IMHO almost all users prefer the 'Set confirm on' setting so that each control behaves the same. However, I did have one program meant for head-down, keyboard only data entry and they LOVED the fields that 'moved without hitting ENTER'. It saved them a keystroke for each field that was filled in completely, and they were paid by the amount of data they put in correctly. Ask the users - their opinion is worth a lot more than that of the other developers, although consistency between programs is very important. I've found it to be much more important to please my clients than to adhere strictly to a specific standard - standards change with great regularity. I prefer to think of them as "Guidelines" which I can follow or not, but need to justify not following.

Barbara < stepping off soapbox >

>Some of our apps are written in C++, some in VFP. There is an inconsistency in the way they work in that VFP defaults to moving to the next field on a form when the end of the input field is reached (SET CONFIRM OFF). We're wondering which of the apps we should change to match the other. The C++ guys are arguing that the way VFP does it is not a "windows standard" and they seem to be right. I just tried a simple form in VB and it does not move to the next field when you reach the end of the current field. In fact, I can't find another app that works the way VFP does. Anyone have a resource as to the recommended way to go?
>
>Mike