Quote Originally Posted by jmcilhinney View Post
If you are indeed adding a new column for each new date then that is the exact opposite of how to use a database. You add rows, not columns. If you need to add new data for each new date, you add a row for each date in a table whose columns are created at the outset and never change. Each date row contains an ID that is then stored in other records to indicate what date they are related to.

You really need to change that design. If this is a commercial application then you're providing a poor solution for your customer. If this is an academic project then you will undoubtedly get a poor mark for was is a very poor design.
I understand what you mean but it has to be that way because each row is a student and the added columns are dates corresponding to a register. I'm making it for a tuition center for one of my friends.