Multiple data per item

[VBAWTB]

Ok...I know that the best way to set up a table is to work across (columns) with the items you need to store a piece of data for, and let the data work downword (rows). But what if each item needed 3 pieces of data?
What I have is a list of items, that needs to be updatable, that each month has to have 3 pieces of data stored for each item.
The only way I could think of to do this was to set up a table that has the list of items in it ran downward (rows) so that it could be updated, as a parent table, and then set up a child table for the data. What the user wants to be able to do is work down that list without having to click on anything inbetween each item, and then when completed, be ready for the next month.
I've set up a form and subform for the parent and child tables, but I need a way to move through that list seemlessly as data is entered. Does it sound like I am heading the right direction, or do I need to look at this differently? Please feel free to ask any other Q's as I am sure I didn't explain this very well... =]

 

[Beetle]

It would be helpful if you could post back with more details, such as your current table structure (at least for the tables that may be involved in this issue) and a better description of the nature of your data.

Also,

What the user wants to be able to do is work down that list without having to click on anything inbetween each item, and then when completed, be ready for the next month.

What does this mean? A typical data entry process does not require the user to "Click" anything when moving between fields and/or records. Are you talking about moving from a form to a subform?

 

[missinglinq]

You're describing (I think...your post is a bit fuzzy) a Main Form/Subform scenario. You'd need two Tables, as you've already suggested.

ItemTable
ItemID (Primary Key)
ItemName

MonthlyDataTable
MonthlyDataID (Primary Key)
ItemID (Foreign Key)
MonthlyDateField
Field1
Field2
Field3

Your Main Form would be based on the ItemTable.

The Subform would be based on the MonthlyDataTable.

The Form/Subform would be linked using the ItemID Field.

1. Each month the the user opens the Form.
2. Enters the monthly data (including a Field to identify the month/year) in the Subform.
3. Moves to the next Record on the Main Form.
4. Repeats #2 and #3 until data is entered for all Items.

Access will automatically enter the ItemID in the Subform Records, without user intervention.

Linq ;0)>

 

[VBAWTB]

missinglinq: Yes, that is the scenario...and the tabes are set up as you described with a one-to-many relationship between them, and a form and subform is set up and linked accordingly. If possible, on the subform I do not want it to show any previous records, just a new empty record. There are 3 fields on the subform but only one record will be entered on the subform per parent record from the main form. After entering data, I need the main form to auto increment to the next parent record.
There are over 200 records in the parent table, and I need to step through each one, enter the data on the subform (one row only) and move to the next parent record as quickly and efficiently as possible preferably with out having to use the mouse to navigate. Is this making any more sense? Please help!

mainform..

ID: 1010
Description: Cheese

subform..

field1 ..........field2...................field3
MONTH_____OPENING LBS_____CLOSING LBS <- after entering last field, increment next record on main form
May.............21........................14

This is what the user is requesting in order to expedite data entry. Thanks for your help and sorry for the confusion =]