Larry,

I don't use the MM framework, but I wanted to add one thing to what you've said here. You're definitely going about it the right way by calling a WebService on the front end to get/save your data, but I'd also take it one step further and serialize your DataSet to XML and pass XML back and forth to/from the WebService. Passing a DataSet back and forth *does* work, but keep in mind if you do it that way that the WebService will probably not work for other applications that are not .NET apps. If you're 100% sure that nothing but a .NET app will access your WebService, then it doesn't matter if you're passing DataSets. Still, nothing's ever 100% ... use XML instead. =)

~~Bonnie



>Thanks Kevin thats clears up some of my misunderstanding of the business object. So if I get this you can have a webservice that returns the DataSet from the business object. Then call the webservice on the front end get the ds assign it to a new business object and make changes to the ds. Then get the ds.GetChanges() which passes a ds containing just the changes. Pass the ds with the changes to a webservice that creates a business object and call the SaveDataSet and pass it the ds with the changes in it. Am I totaly in outer space here or does this sound like it will work ?
>
>Thanks
>
>Larry G Hawke