SQL- Update Table

[Layla]

if there is anyone who can help I would be so grateful!

I have 2 tables
1 - tblPER with fields strPER and Report(Y/N)
2 - tblPerformance with fields such as strDescription strPER etc....

on a frmPER bound to tblPER is a check box that is bound to the Report
field. when this is checked I need to add 13 new records to
tblPerformance with specific data in the field strDescription (these
are for eg Cost, programme, variation...) in these 13 new records I
also need to record in tblPerformance!strPER the PER for which the
check box has been checked.

thus:

tblPER
strPER Report
N186 true

tblPerformance:

strDescription strPER

Cost N186
Perfomance N186
Variation N186

If anyone can make head or tail of this and can help me I would be so
appreciative!

[Eric Schittlipz]

"Layla" <la*******@hotmail.com> wrote in message
news:78**************************@posting.google.c om...

if there is anyone who can help I would be so grateful!

I have 2 tables
1 - tblPER with fields strPER and Report(Y/N)
2 - tblPerformance with fields such as strDescription strPER etc....

on a frmPER bound to tblPER is a check box that is bound to the Report
field. when this is checked I need to add 13 new records to
tblPerformance with specific data in the field strDescription (these
are for eg Cost, programme, variation...) in these 13 new records I
also need to record in tblPerformance!strPER the PER for which the
check box has been checked.

thus:

tblPER
strPER Report
N186 true

tblPerformance:

strDescription strPER

Cost N186
Perfomance N186
Variation N186

If anyone can make head or tail of this and can help me I would be so
appreciative!

You could make the code a lot easier if you had a third table which had list
of these descriptions. If you did that, you might consider giving it a
primary key that was not the name, eg:

tblDescriptions:
DscID DscText
1 Cost
2 Perfomance
3 Variation

So you would have to adjust tblPerformance so it now stored the ID of the
record, not the text. You could also use an index to prevent, for example,
two "Cost" records per parent record. This would be a more standard design
than the two-table approach.

In fact, if you did it like this, you could have a subform based on a
left-join query so it looked as if you had all 13 records present - just
waiting to be filled out (I assume you have more than two fields in your
tblPerformance otherwise there wouldn't be much point in having it)