BullHalseyUSN
Technical User
Guys,
One things that's struck me about access as I've been designing in it is the unwieldiness, in a certain regard, of the subform.
I have a database with tblMember and another tblSchools. To the data entry user, a member's schools are part of one holistic thing we could call the member's record. To a database designer, there are good reasons to split off something like schools attended - normalization and other performance and logical advantages.
The user doesn't need to know that the two elements are from different tables. It seems to me that Access makes it hard to mask this.
What are your techniques to make a subf as "integrated" as possible, please?
TIA
One things that's struck me about access as I've been designing in it is the unwieldiness, in a certain regard, of the subform.
I have a database with tblMember and another tblSchools. To the data entry user, a member's schools are part of one holistic thing we could call the member's record. To a database designer, there are good reasons to split off something like schools attended - normalization and other performance and logical advantages.
The user doesn't need to know that the two elements are from different tables. It seems to me that Access makes it hard to mask this.
What are your techniques to make a subf as "integrated" as possible, please?
TIA