A
Afrosheen via AccessMonster.com
First of all, thanks for reading this post.
I have one table with lots of fields in it. The field I'm concerned with this
post is [shift]. I've created filters which will filter out Day Shift or
Night Shift. I've created a tabbed formed with two subforms with the exact
same info except they are Tab 1 is Day Shift. Tab 2 is Night Shift and
filtered accordingly. So that means twice the programming. For example if I
have to change one item in tab 1 subform then I'd also have to change it in
tab 2 subform.
The dumb question is which would be more efficient putting all the fields on
blank tabs or using the subforms? I know I'd somehow have to come up with a
way for the Day Shift and Night Shift to be filtered on each tab.
Instead of using filters, would it be better to build an SQL string?
I don't know. That's why I call it a dumb question.
Thanks again for reading this.
I have one table with lots of fields in it. The field I'm concerned with this
post is [shift]. I've created filters which will filter out Day Shift or
Night Shift. I've created a tabbed formed with two subforms with the exact
same info except they are Tab 1 is Day Shift. Tab 2 is Night Shift and
filtered accordingly. So that means twice the programming. For example if I
have to change one item in tab 1 subform then I'd also have to change it in
tab 2 subform.
The dumb question is which would be more efficient putting all the fields on
blank tabs or using the subforms? I know I'd somehow have to come up with a
way for the Day Shift and Night Shift to be filtered on each tab.
Instead of using filters, would it be better to build an SQL string?
I don't know. That's why I call it a dumb question.
Thanks again for reading this.