>Is there a best practice for dealing with recursive sections on a form? Is
>there a way to break it into multiple views and be able to go between the
[quoted text clipped - 7 lines]
>
>Jeremy Blawn
Jeremy,
Can you spell out what kind of data you want to collect / display and
what the user needs to do. With that information we might be better
able to suggest an approach.
Andrew Watt
MVP - InfoPath
Jeremy Blawn - 06 Dec 2004 18:45 GMT
Andrew,
We are attempting to model educational standards which have an inherent tree
structure to them. A standard may have many standards underneath them with
required/optional fields. The user would be merely adding new standards or
editing old standards contained in the XML. Nothing fancy, no webservices or
data connections, or having to post anywhere.
The problem is that it's impossible to tell where you are in the tree once
you start adding "child" standards. They are barely shifted to the right and
it becomes a mess very quickly. I was looking at moving children to a button
that takes you to a different view, but read somewhere that it was impossible
to do with recursive sections.
It all comes down to presentation in this case. Let me know what you think.
Thanks.
Jeremy Blawn
> >Is there a best practice for dealing with recursive sections on a form? Is
> >there a way to break it into multiple views and be able to go between the
[quoted text clipped - 16 lines]
> Andrew Watt
> MVP - InfoPath