G
Guest
Scenario: When adding a donor to DonorMaster table the table is updated; also
during this function I want to load, to each of the sub tables, the donor
number and the reference number. I do this by having setup a relationship
between tables (See below). Control Source for the Add Form is an embedded
query and identifying each Recovery_ID Field. The ID’s are than loaded using
VB coding Subtable_recovery_ID = DonorMaser_ID.
Works until I hit the following 2 conditions:
Condition 1:
DonorMaster DonorNumber Primary Key
Recovery ID
Additional Fields
SubTable1 ST1_DonorNumber Primary Key
ST1_Recovery_ID
Additional Fields
Tables 2-29
SubTable30 ST30_DonorNumber Key
ST30_Recovery_ID
Additional Fields
Relationship between DonorMaster and SubTables
1. 1 to 1 relationship based on Donor Number
2. Enforce referential Integrity
3. Cascade Update
4. Cascade Delete
Problem 1: Creating relationship on any table over number 27, get message
“Too many indexes on DonorMaster.â€
Question: Is there a way around this?
Condition 2:
Using embedded query has the potential to bring in huge amounts of unwanted
data.
I only want to place an empty record, except for donornumber and
recovery_id, in these tables.
Question: Can this be done?
Last Question: Should I rethink the design?
during this function I want to load, to each of the sub tables, the donor
number and the reference number. I do this by having setup a relationship
between tables (See below). Control Source for the Add Form is an embedded
query and identifying each Recovery_ID Field. The ID’s are than loaded using
VB coding Subtable_recovery_ID = DonorMaser_ID.
Works until I hit the following 2 conditions:
Condition 1:
DonorMaster DonorNumber Primary Key
Recovery ID
Additional Fields
SubTable1 ST1_DonorNumber Primary Key
ST1_Recovery_ID
Additional Fields
Tables 2-29
SubTable30 ST30_DonorNumber Key
ST30_Recovery_ID
Additional Fields
Relationship between DonorMaster and SubTables
1. 1 to 1 relationship based on Donor Number
2. Enforce referential Integrity
3. Cascade Update
4. Cascade Delete
Problem 1: Creating relationship on any table over number 27, get message
“Too many indexes on DonorMaster.â€
Question: Is there a way around this?
Condition 2:
Using embedded query has the potential to bring in huge amounts of unwanted
data.
I only want to place an empty record, except for donornumber and
recovery_id, in these tables.
Question: Can this be done?
Last Question: Should I rethink the design?