Roger Lovelock wrote: > OK - I've thought about this. Please correct my logic if I am wrong! > > - my new bizObj code is in biz - it is basically a clone of my existing > bizObj (but without the validation code etc) but is created seperately as > the data for the report may be selective while my main bizObj is all > inclusive.
You could (should?) use the same bizobj, just instantiate another copy of it, for the purposes of reporting. In you reporting instance, you could setWhereClause() appropriately. > - I can create the instance of this bizObj only after the selection > criteria has been entered ie in the FrmReport routine in ui. Since this is a > dDialog object self is referring to this dialog and I can do a self.refresh > to get my cursor. dDialog has a refresh() method, but it doesn't do anything with the biz (it repaints all the controls). biz.requery() is what you are looking for. > - The getDataset routine in db can then read the cursor from the > bizObj on the FrmReport dialog (maybe I should just get the dataset within > the FrmReport object and don't worry about having a seperate routine in db?) Yeah, do that. All you need is biz.getDataSet(). > Thats the design stage - hopefully I have both concepts and philosophy right > here and I can go on to the coding/implementation now. Don't get too hung up on designing everything before experimenting with how you would code it. Python development is fast. You get near-instant feedback on whether something will work or not, and when you find something that works it is highly likely to be the "right" design, at least for now. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
