one data entry form multiple records

[javablood]

I have a data entry form that works but I think it is not efficient. For
example, multiple data are entered for the same location and date.
Therefore, it would be more efficient if on the form I could use the the same
location and date to enter the data like so:

Location Date Parameter Value Units
1 D1 P1 V1 U1
2 D1 P2 V2 U2
3 D1 P3 V3 U3
and so on . . .

It sounds good in principle but I am not sure if it can be done and right
now I do not know how to go about doing it.

Any help is much appreciated. Please be specific because I am still on the
steep part of the learning slope.
Thanks,

 

[Klatuu]

The first thing is you database is not well normalized. You should actually
have two tables here. One with the location and date and a child table with
the parameters. It would be a good idea for the location table to have an
autonumber primary key that you could use in the parameter table as a foreign
key.

Then, you would use a form/subform where the main form would have the
location and date and the subform would be use to enter the parameters.

 

[javablood]

Dave,

I am not sure what you mean "child table". Is this just a separate table
with a common field to the "adult table"? If so, then what would be the
common field?
The autonumber?

If I was to split the table, how is that best done with thousands of records?

thanks,

 

[Klatuu]

Yes, the parent table should have an autonumber primary key field and the
child table should have a foreign key field (long integer) that defines which
parent record it belongs to.

You can split the table using some append tables.
First, create both tables in design view.
Now use an append query to append the location and date fields to the new
Location table.
The use an append query that joins the new Location table to the original
table so you can match the records in the new Parameter table to the new
Location table by putting in the parameter values and populate the foreign
key field with the value in the new location table's primary key field.

 

[javablood]

thanks, I will give that a try. Is this the same as having a subdatasheet
and linking the child fields?

 

[Klatuu]

In theory it is similar.