Not "at the top of a Table". Your users shouldn't be entering data directly into tables. You can set up some text boxes in the header of a continuous form for users to enter new information. A button click can use code to append a new record with the values from the text boxes.
I hadn't thought of that. I did have a read-only form in datasheet view based on the table but wanted to have a new record field appear upon opening the form and still see all the records below it.
Your suggestion will work fine. Thanks again!
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).
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.