D
dan.neely
This is access 2003.
I'm making a form to create new records in a main table and
simultaneously allow the user to create records linking them to data
from a second. The link table data is shown as an embedded form
within the main form. The link table has two columns to store foreign
keys from the main table and a lookup table. I want it to have a
compound primary key composed of the two foreign keys.
The problem is that if I have the compoundPK set and then create a new
record in the main form/table or have the secondary form set to link
MainTablePK between the child and master forms Access crashes to the
desktop. If I remove the compoundPK from the link table or the link
between the fields of the two tables the application doesn't crash.
I can move between existing records in the main table without error
even if they don't have any presence in the link table, but the moment
I begin to enter data into the new record I crash access.
I'm making a form to create new records in a main table and
simultaneously allow the user to create records linking them to data
from a second. The link table data is shown as an embedded form
within the main form. The link table has two columns to store foreign
keys from the main table and a lookup table. I want it to have a
compound primary key composed of the two foreign keys.
The problem is that if I have the compoundPK set and then create a new
record in the main form/table or have the secondary form set to link
MainTablePK between the child and master forms Access crashes to the
desktop. If I remove the compoundPK from the link table or the link
between the fields of the two tables the application doesn't crash.
I can move between existing records in the main table without error
even if they don't have any presence in the link table, but the moment
I begin to enter data into the new record I crash access.