I agree you shouldn't put data directly into a table. You should try and interface with an 'external schema' rather than the raw data. This insulates the user view from the precise detail of how things are stored, so you can change the base tables as you see fit. Access has a powerful view mechanism that we know as 'queries'.
That said, I don't agree you should avoid entering data into grids. It's such an easy and powerful feature of Access. Once you start fiddling about with text boxes - well you might as well start programming in Visual Basic or something.
My advice is simple - when you use a package where the empty field is at the bottom then embrace it. Really - why do you need to put it at the top? What is the point?
Go with the flow and you will bring infinitely greater value to your customer. Trying to spanner in precious preferences is the road to long-delayed and over-budget projects. Believe me, I see it all the time (sob).