I'll admit to leaving comments behind when I'm designing new stuff but want to be able to refer to the old stuff, but I only leave it there when I forget or get distracted before finishing the new function.

This, ladies and gentlemen, is the Dunning-Kruger effect in action.

Don't worry, you're not the only one. Besides, that's a good thing: It means you're learning. It also means trying to build any project that takes more than a couple weeks to build ends up taking an eternity as you continuously go back to make older stuff better, always learning just enough more to need to go back and improve the old stuff continuously.

Good to know. Given that I'm at this point just trying to figure out how to use SQL in C#, it's good to know which pieces to avoid. So yes, that answer was useful, even if it didn't actually answer my specific question.

Okay, so I'm thinking my problem here probably involves completely misunderstanding the use of a DataGridView, but here goes: I'm currently working on learning how to use SQL with C#/.NET using VS2010. I created a DataGridView that's linked to my data table. Adding rows to the DataGridView while the program was running did not actually save the changes to the database, so I created a separate piece using SqlConnection & SqlCommand. This successfully added the rows to the database, but did not update the DataGridView. So I suppose there are two questions here: How do I save the changes to a DataGridView to the bound data table? and How do I have the DataGridView reload table data?