Parent-Child Structure - InfoPath Dev
in

InfoPath Dev

Parent-Child Structure

Last post 06-27-2006 11:09 AM by Greg Collins. 1 replies.
Page 1 of 1 (2 items)
Sort Posts: Previous Next
  • 06-26-2006 02:05 PM

    Parent-Child Structure

    I have a form that has the main datasource as an Access database. The database contains a parent and two child tables. The relationship is one (parent) to many (either child). The parent table contains overview information and the child tables are contact and revision information in repeating InfoPath tables.

    Problem: If I fill out the parent table information but don't fill out any child information (not required), InfoPath is automatically adding a row to the child tables in Access. The rows contain the key information from the parent and all other fields are blank. Even if I blank out the key fields in the child table, InfoPath autofills the keys when I submit.

    Is there a way to get around this? I only want to have child rows if information was actually added to the repeating table. Otherwise, I have a bunch of blank rows (with key info) in my database.

    Thanks,

    Chip
  • 06-27-2006 11:09 AM In reply to

    The fact that the fields were present (whether you filled them out or not) is likely the reason why the row was added in the database.

    Repeating tables can have zero rows. I would venture a guess that if you removed that blank row in your InfoPath table before submitting that a new row would NOT appear in your database table.

    If this is the case, then you can default your InfoPath table to not have a row by default. The user would then be required to add a first row if they want to fill in information in that table.
Page 1 of 1 (2 items)
Copyright © 2003-2019 Qdabra Software. All rights reserved.
View our Terms of Use.