M
Marie-Lynn
I have ParentForm and ChildForm, Form and subform respectively. The
relationship in the form is the EntryNumber, which is an autovalue.
I was getting the oft talked about 'The changes you requested to the table
were not successful because they would create duplicate values in the index,
primary key, or relationship. change the data in the field or fields that
contain duplicate data, remove the index, or redefine the index to permit
duplicate entries and try again."
I went back to the original ChildForm table and discovered that the root of
this error is there. Where there is always an entry for ParentForm, there is
only sometimes a corresponding entry for ChildForm. This would not be
problematic of the ONLY time I used ChildForm was when I also used ParentForm
first. However, sometimes ChildForm does not have a relative entry in
ParentForm. This is causing problems because if I hit 'new entry' for
ChildForm, the autonumber sets to the first *available* integer, where this
integer is definitely already related to a ParentForm that has an entry but
its ChildForm does not. You follwoing me?
(This last paragraph was mostly to demonstrate that I am trying to find the
cause of the problem )
How can I make it so that my Form-SubForm relationship will allow for the
use of Parentform independently and also the use of the ChildForm
independently but also allow for the relationships, where ParentForm and
Subform are correlated WITHOUT getting the icky error that doesn't allow you
to save and is aggravating in its repetetiveness?
What. Am. I. Doing. WRONG???
relationship in the form is the EntryNumber, which is an autovalue.
I was getting the oft talked about 'The changes you requested to the table
were not successful because they would create duplicate values in the index,
primary key, or relationship. change the data in the field or fields that
contain duplicate data, remove the index, or redefine the index to permit
duplicate entries and try again."
I went back to the original ChildForm table and discovered that the root of
this error is there. Where there is always an entry for ParentForm, there is
only sometimes a corresponding entry for ChildForm. This would not be
problematic of the ONLY time I used ChildForm was when I also used ParentForm
first. However, sometimes ChildForm does not have a relative entry in
ParentForm. This is causing problems because if I hit 'new entry' for
ChildForm, the autonumber sets to the first *available* integer, where this
integer is definitely already related to a ParentForm that has an entry but
its ChildForm does not. You follwoing me?
(This last paragraph was mostly to demonstrate that I am trying to find the
cause of the problem )
How can I make it so that my Form-SubForm relationship will allow for the
use of Parentform independently and also the use of the ChildForm
independently but also allow for the relationships, where ParentForm and
Subform are correlated WITHOUT getting the icky error that doesn't allow you
to save and is aggravating in its repetetiveness?
What. Am. I. Doing. WRONG???