a single subform that showed all the assets and fixes for a single user might
be fine; the concern is that the volume of detail might be too high. I've got
about 15 fields for information on assets, and about 12 fields on fixes. The
number of assets per user is usually small, and probably has a maximum of
about 6. The number of fixes (for example, Microsoft security updates) could
be very high. That led me to think that a subform for the asset with a
subform for the fixes might work.
On the other hand, perhaps I should consider using a tabbed form instead as a
single subform, linked to the user by the asset ID. The number of fields does
make a Single form a logical choice in either case.
Having only one level of subform might make searching much simpler - that's
the one place where I expect VBA will be essential if I don't leave the user
to make use of just the built-in search tools in Access (a knowledgable user
could do that, and use the result without VBA, but I think it might not be
very user friendly). . I haven't figured out how to design the search yet,
but I think basing it on Allen Browne's approach at
http://allenbrowne.com/ser-62.html using the result to open the nested
form/subset set might work well. I'm not sure of how DoCmd Openform would
handle nested subforms, though.
thanks
twas
John said:
I have a database that tracks 3 levels of information: people; each person
has zero or more assets; each asset has zero or more fixes. The natural way
[quoted text clipped - 5 lines]
What sort of VBA is required to make this all work smoothly for the user?
None whatsoever, if the Assets form is changed from the default
Datasheet to Single.
If you want a continuous or datasheet subform within a continuous or
datasheet subform... tougher. In A2002 or later you can have
Subdatasheets (which can be a real pain), or you can have two
correlated subform continuous subforms; but might a Single subform for
assets be acceptable?
John W. Vinson[MVP]
