You may have already seen this but in case you haven't, take a look at How to: Insert New Records into a Database[^] on MSDN.
JUNEYT wrote:
I don't understand why do I have to assign a new row for the table if I have already bind all the fields in the form to fields in the table in dataset.
You have to assign a new row so that there is somewhere for the new data to go. An empty table has no rows and therefore does not have anywhere to put your data. If your table already has data, your controls will be showing that data and any changes to their contents will change the existing data, therefore requiring a new row as before. Something has occurred to me. When I was starting out with DB stuff, I had a similar mysterious problem. In my case it was something really silly. You might want to check this for your application. If you select your database in Solution Explorer then hit F4, the Properties Window will open for the file. Fairly near the top you should see a 'Copy to Output Directory' entry. Is that set to 'Copy Always'? If so, change it to 'Copy if Newer' because otherwise what happens is that every time you run your app, the empty DataBase is copied over the one with the data in it. Oh how I laughed, when I found that. NOT!! :)
Henry Minute Do not read medical books! You could die of a misprint. - Mark Twain Girl: (staring) "Why do you need an icy cucumber?" “I want to report a fraud. The government is lying to us all.”