Thanks Tim,

I understand that anything I can do in Dot Net, I can do with the Framework, but I was hoping the Framework would provide a built in way to provide this functionality without having to modify the basic design of the framework.

To answer some of your questions, my data backend is SQL Server. I would like to use grids and/or navigationtoostrips but only for selection and navigation purposes not for editing. The editing would be done in standard textboxes etc. It seems that the basic navigation logic in the Framework prohibits me from navigating without first saving changes etc.

It seems to me to be a lot of work to work around the navigation logic built into the Framework. Any ideas?

Sam

>Hi Sam,
>
>Based on the way the jump start interface works you are correct as a single record is edited at a time. You could do this, but what is involved depends on how you are designing your interface.
>
>What type of control (s) would you present for the user to edit the records? If textboxes and such, then how would they navigate to the next record to edit it? Also, what would be your data backend? Behind the scenes, the data representation is standard DataSets with a corresponding Typed Entity and a List collection of Entities. Anything you can do in Dot Net, you can do with the Framework.
>Tim
>
>>I am trying to understand the overall design of the Mere Mortals framework. After experimenting with the jump start, it seems that the framework expects the user to edit one record at a time and then save those changes before moving onto another record. If the user attempts to move to another record without saving the changes to the first record, they are asked if they want to save the changes. Answering No to that question seems to cancel the changes to the first record and then move onto the next record.
>>
>>I am a C.P.A. and in my world we work with a group of accounting transactions at a time. We may have several debits and several credits that need to be edited and saved together as a group. We may add new records or delete records or edit existing records but we want to save the entire group of records all at one time. I have experimented with the ImmediateDelete property of the Business Object to keep the framework from propagating deletions to the backend database immediately. But after deleting a record in the business object's datatable, I seem to be prohibited from doing anything with any other record until I either save the changes by answering Yes when prompted because I want to move to another record, or answering No which cancels the deletion.
>>
>>I must not be seeing the forest for the trees. Certainly there must be a way built into the framework to accomodate working with a group of records before saving all of them at one time. I never want to use grids for editing, I just want to be able to edit multiple records one at a time and then save all the changes.
>>
>>Sam Tenney