Ed,
This is related to the pull down list question.
OK, I got the list working on the edit form.
Then, I wanted to use the same list on the browse and
select screens. It seems like a waste of memory and
time to generate the list separately in each place.
There is also the issue of what if the table for the
pull down list gets updated -- how do you update the
lists (or tuples) used in the pull down list(s).
It seemed to me that a good approach would be to make
the business object for the child table responsible
for offering up key/name lists (or tuples) for use in
pull down lists on the forms for parent tables. The
forms for the parent tables would just get a reference
to the lists (or tuples) in the child table business
object. When the child table gets updated, the
business object will know about it, and can regenerate
the lists/tuples once and for all.
I went ahead and implemented a default generic
solution in Base.py, and the only customization
needed in the table-specific business object
subclasses is to fill in the query and the function to
return the displayed name.
But then when I tried to make it work, I do not know
how to access the business object for a table not
involved with the particular form. The child table is
called Site (or site), and neither
self.Form.getBizobj('site') nor
self.Form.getBizobj('Site') are working in the form
for the parent table.
What do you suggest?
Thanks,
Rick
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
