Printable View
If you run the program, it is the fourth icon counting from left to right, which is the mnuInser_Click sub routine. This routine is the insert part. After you insert, the third icon from left to right is the datagrid that is not reflecting the inserting. The sub routine of that is mnuLog_Click.
ljCharlie
What a mess :p ! Dude , you have to re-code that really . It would be difficult to find bugs , continue developing it . No offense meant but that's just an advice . And one more thing , create your database objs with code , don't use controls objs .They Might be faster but buggy , slow things down , and rare you'll find someone to offer help and the most important is you lose re-usability of your code . Anyhow , I created a demo to show you how easy to solve your problem if it was written that way . It updates as soon as you add new record . Try it you might need to reconsider your code .
Thanks for the demo and your suggestion. Anyway, I figured out how to make it refresh now. I guess using those objects are easy but harder to debug. I have decided not to use this:
DataGrid1.DataSource = DataSet1.table1
DataSet1.Clear()
DataAdapter1.Fill(DataSet1)
Instead, I declared a variable to be a datatable and then fill that table with the records, and then bind that table to the datagrid. Somehow this way it works.
When I have more time on my hand I will convert that project to using code to populate the datagrid. It seems to me that by using code I can controll it better...I just thought that since VB.NET made it so easy to use those objects...I might try it...but it proves to be a pain to debug them.
ljCharlie