Hi all, I would like to say thank you for your tips, I learn a lot on this site from reading other people post. I have a question/wondering if it is possible. I would like to create a daily check list with two boxes yes and no. and i would like the database to save my results for that day. Then the next day resets the checklist so i can enter the values for that day. And i would like it to keep a record of the previous days. Thank You
create a checklist
- Thread starter scopes456
- Start date
The short answer to your question is "Yes" it is possible to do exactly what you want to do.
You would need to create a table with a date field with the default value set to Date or Now and a Yes/No field for each of the options you want to track. You would then need a form that you would use to do the data input.
The very simple description above is only a starting point. Not knowing any more details than what you provided it is impossible to provide any more info. Hope this helps get you started.
You would need to create a table with a date field with the default value set to Date or Now and a Yes/No field for each of the options you want to track. You would then need a form that you would use to do the data input.
The very simple description above is only a starting point. Not knowing any more details than what you provided it is impossible to provide any more info. Hope this helps get you started.
Mr. B Thank you very much, you gave me a starting direction. I am a newbie to access. The goal i am trying to get to. i will have a list of items that i would like to complete everyday. A yes and no box next to each item.Then at the end of the month i could look at a report to see how many times i did "item a" , "item b" and so on. Sorry if i seem a bit confusing.
It is very easy for anyone that is new to Acces to be somewhat confused. You are in goog company. We have all been there.
You first need to create your database structure. It is critical that it be "normalized". I realize that you have said that you are creating a "simple" database but databases have a tendency to be a bit more intense than might be thougt on the surface.
Start by what you believe to be the tables you need. Then you can create the relationship you need between the tables.
Forms are for data entry. They will come later after you have your database structure correct.
Hope this helps.
You first need to create your database structure. It is critical that it be "normalized". I realize that you have said that you are creating a "simple" database but databases have a tendency to be a bit more intense than might be thougt on the surface.
Start by what you believe to be the tables you need. Then you can create the relationship you need between the tables.
Forms are for data entry. They will come later after you have your database structure correct.
Hope this helps.
Mr B, Thank you again for your help. I attached a screen shot of what i did so far. i created a table. the column that is label DAL # is the different equipment i want to track daily. And the other columns shows the different options, with the date. I was wondering , is this the right direction i am going in. My goal is for example 172915 , i performed a PIV today so i check the box, and the next day i didnt used it so i check the Box "not used". how can i make it , so i can look back at history and select 172915 , and see how many time it was "not used" or in "gse".
Attachments
You will not be able to accomplish what you want to do with just one single table.
You will need a table with the Equipment info and then another table what has records created each day indicating the equipment that has had the actions performed on it.
You have a one to many situation here.
This is what I was talking about when I mentioned "normalizing" the database.
You have to get the table sturcture correct before you can worry about forms or queries or reports.
You will need a table with the Equipment info and then another table what has records created each day indicating the equipment that has had the actions performed on it.
You have a one to many situation here.
This is what I was talking about when I mentioned "normalizing" the database.
You have to get the table sturcture correct before you can worry about forms or queries or reports.
Similar threads
- Question
