I just finished a post about upgrading to csla 2.x so maybe that will solve my problem. Currently I am using 1.x
When I edit an item in a child business collection, I only get a byval copy of the item. I change it and then have to delete the original and put the new item into the collection. Now when I save, I have delete the original in the db, and put in a new one. This can be a real headache if I have db constraints due to foriegn keys pointing to the child collection objects.
Am I doing this all wrong or is there a way to directly change the child object in the child collection instead of replacing it and so then I only have to do an update in the db.
Thanks
Yes, I just worked through the collection to get the index of the item I want to modify and set that item point to the new modified item.
Thanks
Brian,
Sorry to jump in here off topic but I couldn't find a way to email you directly. I need to implement the whole Grandchild collection scheme you guys were posting about and was wondering if I could please have a copy of the SafeDataRowReader class (C#). It would be a big help. Is it posted online somewhere?
Thanx!
J'son
Copyright (c) Marimer LLC