Just to be clear, do you know that a tab and subform are different things entirely? A tab is not bound to any table, you can only do that with a subform. The tab just let's you spread things over several pages.
The relationships only matter in a form/subform if there are linked fields that you need to carry over. The main form should consist of a primary key and should be unique. The subform should have a corresponding foreign key that doesn't have to be unique.
No I didn't know that, I thought you had to put a subform on a tab page. Interesting. I think the whole relationship thing is really messing me up. I just created a whole new database to try again and it still isn't working. I create a form, then put a subform on that page, and when I try to enter data on the subform (on that page) it gives me an error. But I can enter the info on the main form on that page.
The error is "You can't assign a value to this object.
*The object may be a control on a read-only form.
*The object may be on a form that is open in Design view.
*The value may be too large for this field."
I know it can't be the middle choice it gives. But I can't find where it might be read-only, and really dont think it is. I don't think it is the last choice either. So I don't know why it is saying that. That was a problem I had with the last database too.
When you say the subform should have a corresponding foreign key that doesn't have to be unique, do you mean that this doesn't have to be an identical name in the form? Like for example,in an Applicant form, I have ApplicantID as the primary key, so in the subform, I can have ApplicantID and it doesn't have to be a primary key, but can link the two together? What if I have other forms as well, which I do, will they all contain the ApplicantID so they can all link?? But on those they will be considered the foreign key?
Thank you so much!!
51
