During every requery, closing the form, etc. if I've made zero changes to the main bizobj and zero changes to child bizobjs, every single record is iterated over in both the parent, its children, its children's children, etc.
You can see the slowness in the OneToManyApp demo even with limiting the resultset to 20 records, which only has one parent and one child. Especially if you first visit each parent record, which fills in the children for each parent. Ed, what do you think about a reverse design that sets a flag when some field has been changed, and resets that flag after a requery? That way only that flag needs to be queried on parent and children in isAnyChanged(). The other idea I have is to maintain a table-wide memento instead of record-wide memento's, and then compare equality of them with the recordset later but not by iterating them. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev
