Larry Bradley wrote: > As mentioned before, I'm converting a large app from VFO to DABO. Many of > the forms use page frames. For example, the form to edit a members' data > has many pages (and bizobjs): the member data on one page. The spouse on > another. Children on another. Boat data on another; Moorings on another. > etc. In VFP this works well: one form with pages allows the user to easily > access and edit all the data for a member. > > Is this a viable scenario using DABO? I see that the class designer > supports page frames. What about performance issues?
Yes, very viable. As I see it you have one parent bizobj and about 5 children of that parent, plus perhaps some grandchildren and great-grandchildren we don't know about. Regarding performance I'd say try it out with the default RequeryWithParent (when the parent changes, all the children get requeried at the same time) but if it seems to lag (I think you'll find it might) then you can delay-requery only when the user activates a particular page. > I have no problems with changing the way things were done, but I don't want > to make myself any unnecessary work. This is all volunteer labor. I know how that feels! ;) BTW, VFP is an acronym for Visual FoxPro, but Dabo isn't an acronym for anything, so saying DABO seems like screaming to me. :) And welcome! -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users
