Tony,

>< are you creating a Windows Forms or Web Forms application? Is there a reason you're not using automatic data binding rather than manually storing retrieved data in your UI controls...or are you simply setting default values based on the selected vendor? How are you saving data? Are you calling a form-level method, using an MM .NET Save button or calling the business object directly?

What you're describing sounds like a classic "EndEdit" ADO.NET problem. In ADO.NET you must issue EndEdit on a DataRow before changes can be persisted to the back end. MM .NET forms automatically try to issue EndEdit on the current DataRow if you're using standard MM .NET data binding...since you're manually data binding these values (by copying them from a DataRow to the controls) this feature doesn't kick in for you.

The business object class has an optional AutoEndEdit flag that when set to true automatically issues EndEdit for you. This is a little less performant because the business object must issue this on all DataRows in a DataSet because it doesn't have a sense of "currency" as the form does (knowing which is the current DataRow), but this should get you where you need to go.

I'm still not completely understanding your UI scenario, but if you can find a way to automatically data bind rather than copying values manually, you can solve this problem that way.

Regards,