johnf wrote: > On Friday 13 June 2008 02:24:32 pm Paul McNett wrote: >> Ed Leafe wrote: >>> On Jun 13, 2008, at 4:49 PM, Paul McNett wrote: >>>> I could see arguments either way, whether or not a base lookup class >>>> belongs as part of Dabo or not. >>> I think that we need to define just what one means by a "lookup class". >> I'll take a stab at it. >> >> A lookup control is a standard data-bound control, complete with >> DataSource and DataField properties, and provides a UI for the user to >> select an item from a group. The item selected from that list becomes >> that control's Value, and as such gets propagated back to the bizobj. >> >> --- >> >> My lookup controls are a composite of a textbox which does Quicken-style >> quickfills as the user types, coupled with a button with a Caption of >> "..." that the user can push to get a popup form to select the item from >> a grid. They can sort the grid, and change the selection criterea (it is >> a modal datanav form without the Edit page). >> >> The control knows its "RowSource" bizobj, against which it does lookups. >> It knows the KeyField of that bizobj and so knows what to fill in as the >> Value when the user chooses a row in the "RowSource" bizobj. >> >> Paul > > +3 I think Paul has it "spot on". > > Paul, does your solution class have all the info passed?
You subclass it and make the appropriate property changes and method overrides, or just instantiate the base class and tweak the properties of the instance. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[EMAIL PROTECTED]
