Triples entry!

[Debbie]

Does anyone have any suggestions as to why, when I enter a childID
into my childinfo table it adds the childID (3 times) in 3 different
records.

 

[John W. Vinson]

Does anyone have any suggestions as to why, when I enter a childID
into my childinfo table it adds the childID (3 times) in 3 different
records.

Why would you WANT to do this?

Creating empty "placeholder" records is essentially *never* either necessary
nor a good idea. What are you trying to accomplish? What tables are involved?

John W. Vinson [MVP]

 

[Debbie]

Why would you WANT to do this?

Creating empty "placeholder" records is essentially *never* either necessary
nor a good idea. What are you trying to accomplish? What tables are involved?

John W. Vinson [MVP]

Long Story. The database was made by previous manager. There is a
table called Child Acct Table: ChildID: Auto Number
ChildAcctrindebb
ChildInfo Table: ChildAcctrindebb plus many other fields, which
actually have no bearing on what is happening. When the Auto Number is
typed in to the CHildInfo Table, it creates 3 records. The
relationship is based on the ChildAcct field in the ChildAcct Table
and the ChildAcct in ChildInfo Table.
In the forms, first we go in to a form which is just the Child Acct
Table: this is where we set up the ChildAcct: prindebb. Then we go to
a form called ChildInfo which is the ChildInfo Table. It tells us to
do a search in the ChildAcct field for the child we are looking up
(prindebb). Then we click in the continuous form called Child Info.
The first field in the Child Info Form is asking us to type in the
Auto Number from the Child Acct Table. Once we do that, it creates 3
records.
By what I have explained, can anyone help me figure out what is wrong
with the form setup and why it duplicates the Child Acct into 3
records.

 

[Debbie]

Why would you WANT to do this?

Creating empty "placeholder" records is essentially *never* either necessary
nor a good idea. What are you trying to accomplish? What tables are involved?

John W. Vinson [MVP]

The childID is the 4 first letters of childs last name and 4 first
letters of childs first name. That is the code we use to look up
records.

 

[John W. Vinson]

The childID is the 4 first letters of childs last name and 4 first
letters of childs first name. That is the code we use to look up
records.

So Dianne Johnson, Dian Johnston, Diane Johns, and Dianne Johnson (the other
one, not the first one) have the same ID? BAD idea. Names are *not* unique and
do not make good keys!

John W. Vinson [MVP]

 

[John W. Vinson]

Long Story. The database was made by previous manager. There is a
table called Child Acct Table: ChildID: Auto Number
ChildAcctrindebb
ChildInfo Table: ChildAcctrindebb plus many other fields, which
actually have no bearing on what is happening.

Why two tables? What are these fields?

When the Auto Number is
typed in to the CHildInfo Table, it creates 3 records. The
relationship is based on the ChildAcct field in the ChildAcct Table
and the ChildAcct in ChildInfo Table.

WHY does it create three records? That's my question! What's *in* these
records, and how does it create them? What gets put into the fields of these
three records?

In the forms, first we go in to a form which is just the Child Acct
Table: this is where we set up the ChildAcct: prindebb. Then we go to
a form called ChildInfo which is the ChildInfo Table. It tells us to
do a search in the ChildAcct field for the child we are looking up
(prindebb). Then we click in the continuous form called Child Info.
The first field in the Child Info Form is asking us to type in the
Auto Number from the Child Acct Table. Once we do that, it creates 3
records.

That's ridiculous! Users should not even *SEE* an autonumber, much less type
them; a Subform has a Master and Child Link Field, which will automatically
fill in the value from the mainform into the child form record. Is this really
a subform, or are you opening a second form? What are the Recordsources (post
the SQL) for these two forms?

By what I have explained, can anyone help me figure out what is wrong
with the form setup and why it duplicates the Child Acct into 3
records.

What's wrong is that your previous manager apparently did not have a good
understanding of how Access works, and cobbled together something *really*
strange and inefficient.

John W. Vinson [MVP]