Data Entry in SubForms - Access Developer Forum


	Back to Access Developer Forum Comments List

Upload Images @Reply Bookmark Link Email Next Unseen

Data Entry in SubForms

Scott Axton

4 years ago

I really like the SubForm concept given in the ABCD database.
It totally makes sense to me from the stand point of keeping the forms compact and making lots of information available on one screen.

Two pronged question here.
In my Customer table (Entity in ABCD) I have a number of fields that are needed for the record but don't need to have them "up front and in your face" when viewing them.  Does any one know if there are drawbacks to putting those fields in a SubForm and making it one of the "tabs" (Same record - Same Table)?

Part two - while I like the viewing of records and the organization of the data once it is in the tables I find that the form is not very "Data Entry" friendly for large numbers of records.  ( I add approx. 100 records a day at times)

Has any one come up with a way to just keep tabbing through the "Tabs" to keep entering data with out clicking each tab and then each field to enter data?  I hate having to constantly reach for the mouse while typing.

Suggestions anyone?

Richard Rost @Reply

4 years ago

One: no shame in that. It's like the "extended customer info" from X4.

Two: why don't you make a data entry form (continuous or single - whatever works for you) that has exactly what you need in the order you need it? Doesn't need to meet regular normalization rules, just go to town with your data entry and then use queries or a recordset to plop the data in wherever you need it.

For example, let's say you want to quickly type in a new customer's first name, last name, address, and the products he just purchased, but you want to maximize data entry speed, and an order never has more than 3 items on it. So... make yourself a quick data entry table...

Richard Rost @Reply

4 years ago

QuickEntryT: FirstName, LastName, Address, PID1, Qty1, PID2, Qty2, PID3, Qty3

Now, I know what you're thinking... this isn't properly normalized. You're right, but it's only a temp table for data entry purposes. Once you're done and you hit OK, you'll use a couple of recordsets... drop that new customer into the CustomerT, add an order to OrderT, and then add those products to the OrderDetailT.

Boom. Done. It's all about designing a QUICK data entry interface for your needs. This would make a pretty cool video. :)

	Richard Rost @Reply 4 years ago
You know what... I've been wanting to redo the free Recordsets video... this would make a great extended cut (your quick data entry form).

	Scott Axton OP @Reply 4 years ago
Thanks for this! I guess I was over thinking it to much. Outside the box thinking wasn't one of them.

This thread is now CLOSED. If you wish to comment, start a NEW discussion in Access Developer Forum.

Next Unseen

New Feature: Comment Live View