>>If I drop two business objects on a form, object 'Father' and object 'Son'.
>>Then in the Son object, I set it's parent object property to Father, and check it's "New child on new parent" and "Save child on save parent" properties.
>>What is the proper way to wrap the saves of these objects into one transaction?
>>The way I currently have it, the Father can save with the Son failing.
>>
>>And if it makes any difference, these are remote views.
>>

>There are no settings in the BO to handle this.

That's the main thing I wanted to hear I guess. I still feel fairly new to the framework, and anytime I feel like i'm battling against it, I feel I must be doing something wrong.

>
>What you will need to do is bind each of the view connections together through SQLPassthrough and wrap them in a sql server transaction. Once bound, it doesn't matter which connection initiates the transaction.

I'm not sure what you mean by "bind each of the view connections together". Or, I just don't know how to do that. *s*

>A simpler method would be to have each view share the same connection and wrap everything in a sqltransaction.
>=SQLSetProp(lnHandle, "Transactions", 2)

I was thinking of going this route as well.

>
>There is a good discussion on these techniques in "Client/Server Applications with Visual Foxpro and SQL Server", available at www.hentzenwerke.com.

Yup... got it.. good book.

>Recoding the save method in kBizobj would not be that difficult, but I would wait to see what's in the upcoming version.

I too am hoping that the next version deals with SQL Server better. In fact, I'm gonna be taking that next class of Kevin's.

Thanks so much.