I have plans that belong to clients. The clients have relationship managers, analysts and administrators. I would like to be able to search for plans by client relationship manager, analyst or administrator. I would then like to come back and have my plans business object populated with the oines that were selected in the browse dialogue.

Can someone please point me in the right direction so that I can get this done?

TIA.

Marcia

Sorry, I'm almost nuts with some coding myself over here, and didn't really get what you are trying to do...

But the thing is, a Browse Dialog will need a BO type and a BO instance of that type to populate. Once you get back from the BD, your can do whatever you want with that BO populated. You can filter it on some condition and use the SomeBO.CopyDataFrom to get the filtered records from the BO populated by the BD, for example.

Sorry if this has nothing to do with what you need.

Hi Ivan.

Thanks so much for getting back to me so quickly.

I read the documentation on the CopyDataFrom method, but it looked like the 2 business object needed to have the same structure. My problem is that they don't because I want the "searching" BO to be the result of a join between 3 tables and the primary BO in the form to be only one of them. Is there a way that I can use the CopyDataFrom method when the structure of the 2 BO's is not the same?

You can actually still use the CopyDataFrom method between BOs of the same type even if you have extended fields and properties on one BO but not the other. Just be sure to use one of the ClearAndFill copy types when you call the method (if you do an append but the field structure doesn't match it will throw an error.) The target BO will have any extended fields that were included in the source BO, but those fields don't have to be exposed through extended properties if that isn't needed or desired.

Dustin Taylor (09/22/2008)

---

Howdy Marcia ,

You can actually still use the CopyDataFrom method between BOs of the same type even if you have extended fields and properties on one BO but not the other. Just be sure to use one of the ClearAndFill copy types when you call the method (if you do an append but the field structure doesn't match it will throw an error.) The target BO will have any extended fields that were included in the source BO, but those fields don't have to be exposed through extended properties if that isn't needed or desired.

Hi Dustin.

Thanks so much for the response. I figured that there had to be a way to do this because it must be a common requirement in a fully normalized database, but the documentation was not real explicit about how

BTW, I really love what you guys have done. It has made cranking out this application a breeze. We were hired to do a re-write of an application that was a real mess and in less than 3 weeks I have almost duplicated the functionality in their current app and it took the previous programmer a year to give them what they are now using.