On Mon, May 18, 2009 at 2:47 PM, Ed Leafe <e...@leafe.com> wrote:
>
> I guess I don't understand your design. It still sounds to me like
> you have: Account - 1:M - Contact. 'Opportunity' sounds like it is
> related to Account, and only indirectly to Contact. Either way, it
> sure doesn't sound like you have Contact - 1:M - Account/Opportunity,
> so I'm not sure why your examples describe Contact as the parent object.
>
In this particular case contacts are of high value, so there is the
interest/need in the relationships with Contact has the parent.
But, by all means I put it forward more has an example (do I'm dealing with
it in real life).
Having said that, you can programmatically 'switch' your Contact
> bizobj by changing the SQL directly; i.e., by setting the UserSQL
> property. When you do that, none of the 'addField', 'addFrom', etc.,
> values will be used; in fact, they aren't needed at all. Just set the
> UserSQL on the fly to the correct joins for whichever case is your
> current need, and then requery away.
So that would allow for maintaining one Bizobj for Contact?
Would that work like this:
contactBizob_Instance.UserSQL = "New SQL"
self.Form.PrimaryBizobj = contactBizob_Instance
self.Form.requery()
Miguel
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: Dabo-users@leafe.com
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/a19730800905180656j7a0d79ccsc775b2f40df49...@mail.gmail.com
