Pressing enter on a data entry form moves to next record?

[June7]

If that is the behavior you want. If you don't want the form to advance to next record from the last control in the tab order, then set Cycle property to CurrentRecord. They will just keep cycling through the same record, from first control through to last and back to first, round and round. And if you disable the NavigationButtons bar they won't be able move to other records unless you give them custom buttons.

[Missinglinq]

I do, but like most things, it depends on your situation! Unless you're developing an app where you have data entry people in a 'production' situation, i.e. where they're entering a gazillion records all at once (typically done where data from one database is being converted/entered into another database) having the Cycle Property set to All Records is not needed. Having All Records as the default is just one of many (in my opinion) bad default settings Access has.

Linq ;0)>

[Ruegen]

I do, but like most things, it depends on your situation! Unless you're developing an app where you have data entry people in a 'production' situation, i.e. where they're entering a gazillion records all at once (typically done where data from one database is being converted/entered into another database) having the Cycle Property set to All Records is not needed. Having All Records as the default is just one of many (in my opinion) bad default settings Access has.

Linq ;0)>

That is what I thought! It's something I am now going through and checking the settings on every form that includes a subform tied 1-1.

Thanks for your help.