I have a business form that allows users to add and update rows from two tables. They don't lend themselves well to a parent-child relation. Do I need to have a separate set of buttons for each table on the page or is it better to just call the saverow and other update methods for the 2nd table from the buttons bound to the 1st table? I realize that there would be more overhead calling updates for the 2nd table all the time when there may not have been any changes there. Are there other down sides to that? Maybe there's a third possibility I haven't thought of. Thanks in advance.
Linda Harmes
HiBit Technologies, Inc.