On Nov 11, 2008, at 12:51 PM, johnf wrote:
> Wait a second! I was trying to do it your way - using bizobj's.
> You have
> told me many times to use bizobjs. Don't bypass the bizobj's. Keep
> bizobj
> code out of the UI. I could have easily used a tempcursor and
> handled all of
> my requirements. But again I was trying to do your way. Your
> response was
> to filter the data after I retrieved the data. Well, that did not
> work out
> very well due to all the joins and virtual fields associated with
> the bizobj
> in question. And I did not see much difference between what I had
> to do with
> the filtering and just creating a tempcursor.
I suggested adding a separate method of the bizobj, not creating
multiple bizobjs for the same table. A fundamental assumption, which
I've said many times. That's the way that they were designed to work:
biz.DataSource == cursor.Table.
I don't remember all the details of your requirements, but I do
remember that what you suggested was very doable.
-- Ed Leafe
_______________________________________________
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]
