B
Bill H.
Currently using access 2000. I'd like to have a subform on a form, where
the default view of the form is set to continuous (as is the view of the
subform). Naturally, Access doesn't like that.
My first question is whether this is "solved" in later versions of Access.
If not (or even if), how do I implement that ability using Access 2000? And
the kicker is that I would like this form (with its subform) to be a subform
on the main parent form.![Smile :) :)](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
The design is for public services offering, where a family (parent form) has
many services they can choose to participate in (subform) and each of those
services have scheduling dates (start/stop) and a field for
accept/decline/waitlist (the subform on the subform). Thus a family could
choose a service on a date, and after review be denied (on a date), but
subsequently (on another date) be waitlisted, and then on yet another date
be accepted. The history of this accept/decline/waitlist needs to be
tracked.
Thanks!
the default view of the form is set to continuous (as is the view of the
subform). Naturally, Access doesn't like that.
My first question is whether this is "solved" in later versions of Access.
If not (or even if), how do I implement that ability using Access 2000? And
the kicker is that I would like this form (with its subform) to be a subform
on the main parent form.
The design is for public services offering, where a family (parent form) has
many services they can choose to participate in (subform) and each of those
services have scheduling dates (start/stop) and a field for
accept/decline/waitlist (the subform on the subform). Thus a family could
choose a service on a date, and after review be denied (on a date), but
subsequently (on another date) be waitlisted, and then on yet another date
be accepted. The history of this accept/decline/waitlist needs to be
tracked.
Thanks!