Adding new field freezes check boxes

  • Thread starter Thread starter dreamsoul620 via AccessMonster.com
  • Start date Start date
D

dreamsoul620 via AccessMonster.com

Hi all!

Here is my setup. I have a form with a subform. The main form has
instructions for how to view the data in the subform. I also have 4 hidden
text boxes on the main from that carry the data in the subform to another
related form. This related form is set up like a letter. The name and
information for the selected person in the subform is carried over to the
letter. All of the information is pulled from one table in one query.

My problem comes in when I try to add another table to the query. The tables
are related based on Name. I can correctly pull the data I need, but in my
subform my check boxes are disabled. These work great if I remove the second
table from the query. Is there a way around this?

Thanks,
Crystal
 
When you link your name fields together, it probably causes the query
to become "read only" and thus you can't update it. That happens when
you are not joining a table's key value to another value in the other
table. I would suggest using a unique identifier for joining your
tables together and not the name field because Name is not unique (ie
you could have 2 John Smith's)
 
Both tables also share a number field which is always unique. If I make this
the primary key for both tables, would that work?

Jeff said:
When you link your name fields together, it probably causes the query
to become "read only" and thus you can't update it. That happens when
you are not joining a table's key value to another value in the other
table. I would suggest using a unique identifier for joining your
tables together and not the name field because Name is not unique (ie
you could have 2 John Smith's)
Hi all!
Click to expand...
[quoted text clipped - 15 lines]
Click to expand...
 
Yes, it should.

Both tables also share a number field which is always unique. If I make this
the primary key for both tables, would that work?

Jeff said:
When you link your name fields together, it probably causes the query
to become "read only" and thus you can't update it. That happens when
you are not joining a table's key value to another value in the other
table. I would suggest using a unique identifier for joining your
tables together and not the name field because Name is not unique (ie
you could have 2 John Smith's)
Hi all!
Click to expand...
[quoted text clipped - 15 lines]
Click to expand...
Click to expand...
 
I'm not sure I follow this, but you can only have the primary key on one
side of the relationship. If by "share a field" you mean relate the fields
to each other, only one can be the PK.

dreamsoul620 via AccessMonster.com said:
Both tables also share a number field which is always unique. If I make
this
the primary key for both tables, would that work?

Jeff said:
When you link your name fields together, it probably causes the query
to become "read only" and thus you can't update it. That happens when
you are not joining a table's key value to another value in the other
table. I would suggest using a unique identifier for joining your
tables together and not the name field because Name is not unique (ie
you could have 2 John Smith's)
Hi all!
Click to expand...
[quoted text clipped - 15 lines]
Click to expand...
Click to expand...
 
Thanks, that worked perfectly.

Jeff said:
Yes, it should.
Both tables also share a number field which is always unique. If I make this
the primary key for both tables, would that work?
Click to expand...
[quoted text clipped - 14 lines]
Click to expand...
 
Back
Top