>>I've been using the framework for a number of years now, and it is very flexible if you are willing to invest the time to learn it. One of the things I found, though, is that business objects don't have a lot of flexibility in terms of updating records in table buffered cursors. I would like the option of scanning the modified records, updating one record at a time, and the option of presenting a user with oldval and curval if there are any update conflicts. In some situations this would be useful.
>>
>Thanks Jim.
>
>Could you give more detail on how business objects in MM do deal with buffered tables?
>
>Also, when you talk about time to learn it; if we buy a framework, we intend to budget 3 intensive weeks where we concentrate on nothing but learning the framework. Will this get us high enough on the learning curve to be reasonably productive? We are both experienced VFP programmers, really experienced with OOP, and mildly familiar with codebook.
>
>Thanks

The framework does handle table buffering, you just need to remember to send in the correct parameters when issuing a save.

Example: Thisform.oBizobj.Save(1,.t.)

Kevin's documentation is nothing short of Amazing. If you follow the documentation, you can get by without too much pain, but he offers training as well. I am a firm believer in training, even though I learned Codebook the hard way. If I can talk this company into standardizing with MM, I am going to see if we can get Kevin to come on site and give some training classes and help us customize the framework for our needs.

Hope this helps.

Jim