Return to Question

• tblshopstatus - stores dates, monthid, and areaid

• tblarea - stores the shopnames

• tblmonths - stored the monthnames

For any given area I would have just 12 rows a record for each month Back to the void in question, here you see I run an UPDATE for Jan in dateone and then do the same thing again for Feb in dateone. I am using SQL function to increase the value by one month etc... it works.... or it does what I want, it puts 1/1/2018, in dateone on the Jan row, and 2/1/2018 in dateone on the Feb row when the button is clicked, no errors are thrown and the data is updated this verifies to me that the void is working. . .

• tblshopstatus - stores dates, monthid, and areaid

• tblarea - stores the shop names

• tblmonths - stored the month names

For any given area I would have just 12 rows a record for each month, Back to the void in question, here you see I run an UPDATE for Jan in dateone and then do the same thing again for Feb in dateone. I am using a SQL function to increase the value by one month etc... it works.... or it does what I want, it puts 1/1/2018, in dateone on the Jan row, and 2/1/2018 in dateone on the Feb row when the button is clicked, no errors are thrown and the data is updated this verifies to me that the void is working. . .

This snippet works and does as desired, but I just wonder if I am being too repetitive. What I mean by this is, eventually I will have all 12 months in there. So.... 12 Update Queries, 12 Commands, 12 Parameters, 12 values, and 12 executions. All doing similar but slightly different things.

What does this do? - The purpose of this code is to update a table that is used by a Gridview on one of my .aspx pages. The user clicks a Save button which calls this void and the Gridview is updated.

The tblshopstatus has 33 columns 31 to cover the days of the months, monthid, and areaid. So in the end to fill the grid I combine,the three tables into a view in SQL to get the the final grid data. A screen of that is here:

This snippet works and does as desired, but I just wonder if I am being too repetitive.

What I mean by this is, eventually I will have all 12 months in there. So.... 12 Update Queries, 12 Commands, 12 Parameters, 12 values, and 12 executions. All doing similar but slightly different things.

What does this do? - The purpose of this code is to update a table that is used by a Gridview on one of my .aspx pages. The user clicks a Save button which calls this void method and the Gridview is updated.

The tblshopstatus has 33 columns 31 to cover the days of the months, monthid, and areaid.

So in the end to fill the grid I combine the three tables into a view in SQL to get the the final grid data.

A screen of that is here: