I don't think it is realistic to expect anyone to learn a new programming language as though they are just rearranging furniture. Syntax is one thing, but the new languages offer things that require new thinking too. Look where we were when all we could do is jump from one part of the top-down code to another. Now look at OOP and just how much our thinking had to change in between. My biggest problem with new languages is that there are so many now. With the advent of the internet I had to learn HTML. Then ASP and Java script. With more and more complex data structures I had to learn Pascal in the early 80s, and, later, VB and SQL. Then VB changed! Now there's Ruby, Java, LISP, C#, and a whole host of others. What's on the horizon? And the time between new languages is shortening.

Now it's a hobby for me and I don't suffer the pressures most of you have. I want to write an application for my work because it doesn't exist and I don't like my VBA version. So I am learning C# so I can write a WPF application. Thanks to people like all of you I can give it a good shot and maybe something good will come of it.

Thank goodness I don't have to have it reviewed!

As for me I like tuts like this because it helps me clean up my thinking and gives me the syntax I need for putting a new language to use. I use classes and properties in VBA all the time, but there is nothing to compare with INotifyPropertyChanged. That's what I needed. I knew what a property was but read through this tutorial anyway. Glad I did.

Thanks you guys. Both answers are excellent. I was reading C# For Programmers when this question entered my brain. Their example class, of course, didn't deal with this and I was wondering how y'all would treat it.

Thanks again,

Sergio,

That is sort of the plan. I don't want to have to read/write a lot to the DB, so I was thinking of just keeping the changes until I was done working then just write all the changes to the DB. I'm not sure if this is the right approach. It may be that this approach takes more time than an immediate write to the database when a field changes. In any case, I didn't want to have to make sure that I triggered a "wasChanged" boolean in every set. So I thought that if anything changed and an event was raised I could just set the wasChanged value then and not have to include it in every set.

Ryano121's suggestion requires setting a boolean when something changes in the class by trapping the On Click event or something like the Lost Focus event of a form. There again I have to add a line to set a boolean in the active class so I can trap changes and make sure they get into the DB. But what if I just click into a field, change my mind and move on. It would require me to store the contents of the field in a variable when the form field gets the focus, and check it against the contents of the form field when the field loses the focus to see if anything changed.

So one blanket "SomethingHasChanged" event would be great.

Upon further reading and examining the code in the "DataSet.Designer.cs" I am getting an idea. The dataset is already defined. Dragging a table adapter onto a form should create the table adapter in the Dataset designer class. I should be able to set the command and other parameters on that table adapter then execute the fill to get the data.
So how do I get to the data adapters? There must be something like Dataset.Datatable.Tableadapter. And that being the case there would be methods to set the command text, call the fill methods etc.