S
SteveC
I find that the concept of the Master/Detail in InfoPath seems backwards
compared to use of a similar concept in MS Access. It would seem that the
Master section should be the One side and the Detail should be the Many Side,
and the Mant side should use a table to list row of repeating items.
Instead, the Master is always a repeating table, which is very confusing.
My goal is to develop what I hope is a simple solution using a one-to-many
relationship on a form that is disconnected from a database and allows a user
to save each form as an XML file, which can later be imported to Access
tables - basically an Order-Oder Details type situation. Amazingly what is a
simple concept to implement in Access is alluding me in InfoPath.
Am I missing something here, or is InfoPath not up to this task at this point?
Thanks,
SteveC
compared to use of a similar concept in MS Access. It would seem that the
Master section should be the One side and the Detail should be the Many Side,
and the Mant side should use a table to list row of repeating items.
Instead, the Master is always a repeating table, which is very confusing.
My goal is to develop what I hope is a simple solution using a one-to-many
relationship on a form that is disconnected from a database and allows a user
to save each form as an XML file, which can later be imported to Access
tables - basically an Order-Oder Details type situation. Amazingly what is a
simple concept to implement in Access is alluding me in InfoPath.
Am I missing something here, or is InfoPath not up to this task at this point?
Thanks,
SteveC