Is a tabbed subform my best solution???

[painterz]

Hello All,

About 15 yrs ago I created a client db with all of the forms, queries, reports, coding, etc. Since then I've been out of the programming world and have gotten extremely rusty and lost my mad skills I've adapted the client db to be used for a neighborhood directory and all has worked well until now. My db is set as a one to many, one house to many people within the house. Now, I need it to be one house to multiple families then people w/i the family; this would be for those who own and rent the house. Is a tabbed subform my answer? One subform would show the owning family, the other would show the renting family. Is there a better way? Would I need to change my code or just the references to the subforms? I think I should be able to duplicate my code per subform and change the way the form talks to the subform but not sure. Any suggestions, links, references, would be appreciated!

Thanks!

 

[Steve R.]

I would suggest (two) main forms based on the house address and the family, with a datasheet subform showing the related data. For example, all the persons located at that specific address.

The datasheet subform should only display minimal data. This means that you would probably need to have a pop-up form to display all the information from the selected record shown in the datasheet.

 

[painterz]

Hi Steve,

I appreciate your answer. I would like to build on what I currently have since I no longer have the skill set to start from scratch. My main form does show minimal info--address, whether to list in the directory, and rental. The subform has all of the data pertaining to the people. So it sounds like I have the reverse of what you are suggesting?

 

[Steve R.]

My main form does show minimal info--address, whether to list in the directory, and rental. The subform has all of the data pertaining to the people. So it sounds like I have the reverse of what you are suggesting?

Seems that you are very close to what I was suggesting. The question appears to be how the subform is displayed. I don't know how your subform displays the data. I am suggesting that the subform be in "datasheet view". Not as as an individual form, though that would be one approach.

There is one caveat. I found that "datasheet view" works better when it is based on a form not a table. After developing the form, the form's view property must be set to "datasheet view". It will take some experimentation.