I am having some trouble creating a form with a tab control with multiple forms. My table structure is One Farm can have many farmers and one farmer can have many supporting application documents, and many application items purchased. I was able to create a form with the main form with the farm table and a subform in a tab control of farmers but when I tried to add the supporting documents table to another tab there is no relationship directly between these tables can you please indicate how I can get this done.
Solved Forms
- Thread starter Nixx1401
- Start date
strive4peace
AWF VIP
- Local time
- , 18:37
- Joined
- Apr 3, 2020
- Messages
- 1,046
hi Nixx,
If you mean that the second subform is linked to the selected record in another one, you can set that reference in its LinkMasterFields property
Although, for clarity, I prefer to make a calculated control on the mainform with this Control Source:
that is named whatever the field it contains is called, and use that in LinkMasterFields for the subform that needs it
If you mean that the second subform is linked to the selected record in another one, you can set that reference in its LinkMasterFields property
Although, for clarity, I prefer to make a calculated control on the mainform with this Control Source:
=[subform_controlname].form.controlnamethat is named whatever the field it contains is called, and use that in LinkMasterFields for the subform that needs it
strive4peace
AWF VIP
- Local time
- , 18:37
- Joined
- Apr 3, 2020
- Messages
- 1,046
by the way, the tab control is just for grouping and has no effect on referencing another form or control
strive4peace
AWF VIP
- Local time
- , 18:37
- Joined
- Apr 3, 2020
- Messages
- 1,046
strive4peace
AWF VIP
- Local time
- , 18:37
- Joined
- Apr 3, 2020
- Messages
- 1,046
Nixx , I saw your other post ... in my opinion, tab control is better than navigation control! Functionally, they appear to be the same but they aren't. With the Tab Control, all data is accessible even when you go to another page, and it sounds like this is what you want.
The Navigation Control was created to cut down on loading time, but only the loaded page can be referenced. If loading time becomes an issue with the Tab Control, you can load only what shows on the Tab control at runtime, and others as they're needed using VBA too.
The Navigation Control was created to cut down on loading time, but only the loaded page can be referenced. If loading time becomes an issue with the Tab Control, you can load only what shows on the Tab control at runtime, and others as they're needed using VBA too.
Last edited:
strive4peace
AWF VIP
- Local time
- , 18:37
- Joined
- Apr 3, 2020
- Messages
- 1,046
hi Nixx,
navigation forms are NOT easy to use. I highly recommend using a tab control instead. You can still drag subforms from the navigation pane onto it! Just make sure the page you want to put a subform on is selected first
First, before making forms, be sure to set up the relationships between your tables. Here is a video that you and your daughter can watch together ... maybe make some popcorn
Enforce Referential Integrity (RI) on Access Relationships (cc)
It is also a good idea to fill out the field Description column (in table design -- Microsoft's templates generally don't do this), even if all you do is copy and paste the field name into it. That is because the field description will be used for Status Bar Text* when you make forms.
*what shows in the lower left on the bottom line of the screen.
To answer your question, you'll see LinkMasterFields and LinkChildFields on the Data tab of the Property sheet when the subform control is selected. To turn on the Property sheet, press Alt-enter or choose Property Sheet from the Tools group on the Design ribbon tab.
The LinkMasterFields property can contain a control name (or names) that is unbound, unlike LinkChildFields, which must be fields in the record source of the subform. They should also be ON the subform in a control, even if it is not visible.
If the link fields are set, then your code does not need to do anything special for the subreport to show the right records
navigation forms are NOT easy to use. I highly recommend using a tab control instead. You can still drag subforms from the navigation pane onto it! Just make sure the page you want to put a subform on is selected first
First, before making forms, be sure to set up the relationships between your tables. Here is a video that you and your daughter can watch together ... maybe make some popcorn
Enforce Referential Integrity (RI) on Access Relationships (cc)
It is also a good idea to fill out the field Description column (in table design -- Microsoft's templates generally don't do this), even if all you do is copy and paste the field name into it. That is because the field description will be used for Status Bar Text* when you make forms.
*what shows in the lower left on the bottom line of the screen.
To answer your question, you'll see LinkMasterFields and LinkChildFields on the Data tab of the Property sheet when the subform control is selected. To turn on the Property sheet, press Alt-enter or choose Property Sheet from the Tools group on the Design ribbon tab.
The LinkMasterFields property can contain a control name (or names) that is unbound, unlike LinkChildFields, which must be fields in the record source of the subform. They should also be ON the subform in a control, even if it is not visible.
If the link fields are set, then your code does not need to do anything special for the subreport to show the right records
Last edited:
strive4peace
AWF VIP
- Local time
- , 18:37
- Joined
- Apr 3, 2020
- Messages
- 1,046
hi Nixx,
what is most important are the underlying TABLES. Forms are just what you use to add and change data. After watching the relationships video, lay out your relationships diagram and post a screen shot of it here.
Take care to name fields well. don't use spaces or special characters. Underscore is ok ( _ ). the first character should be a letter.
For primary and foreign keys, I keep fieldnames the same since they represent the same piece of information. Others tell you to put pk or fk in your names. Everyone has their own preference. I like to keep it easy
ID is bad for a field name because ID in one table doesn't relate to ID in another table. Therefore, ID should be qualified, like FarmID and CropID.
If the table structures and relationships are good, the rest is downhill
How old is your daughter? Is she doing this WITH you?
what is most important are the underlying TABLES. Forms are just what you use to add and change data. After watching the relationships video, lay out your relationships diagram and post a screen shot of it here.
Take care to name fields well. don't use spaces or special characters. Underscore is ok ( _ ). the first character should be a letter.
For primary and foreign keys, I keep fieldnames the same since they represent the same piece of information. Others tell you to put pk or fk in your names. Everyone has their own preference. I like to keep it easy
ID is bad for a field name because ID in one table doesn't relate to ID in another table. Therefore, ID should be qualified, like FarmID and CropID.
If the table structures and relationships are good, the rest is downhill
How old is your daughter? Is she doing this WITH you?
found a solution. http://www.fmsinc.com/MicrosoftAccess/Forms/Synchronize/LinkedSubforms.asp and
