I have many times read on this forum the 'rule of thumb' which states, "...only one updateable table per view and only one updateable view per business object. I thought I understood this axiom until tonights musings. How does one handle an update that involves child records. For instance, if one creates a new invoice it is necessary to update both the invoice table and the invoice item table. Assuming that the data entry for the invoice and items is handled on the same form, does one place two business objects on the form?
©2001 Virgil Bevans |
