CheckList Database (2000)

Topic

New Reply

This is something i have never done before in Acces sand a bit unsure on what the best approach is going to be, so would really appreciate some tips or pointers to examples.

I need to create a database that is going to store checklists and allow the user to fill in these check lists and duely store the results.

What I am thinking is i have one table set up to hold the check lists something like

tbl_check
check_id, check_checklist_name, check_catergory,Check_question

with check_id being the primary key

then having another table called tbl_results

results_chk_id , results_date,results_client, results_YN

linking the two tables by chk_id to results_chk_id.

but here is where im getting stuck, how would i go about making the user select a check list to fill in, and then show on screen all the questions relating to that check list

regards

Chance

Reply | Quote

Replies

I would create a separate table to hold the checklist ID and checklist name, and another table to hold the questions, with checklist ID, question ID and question text. These tables are linked by checklist ID. The first table will serve as the row source for a combo box from which the client can select a checklist.

Then, a table with client ID and checklist ID (composite primary key). A record in this table signifies that the client has selected a specific check list. Linked to the clients table on client ID and to the checklists table on checklist ID.

Finally, a table with client ID, question ID, result (Y/N), and perhaps also checklist ID (although that could also be derived from the question ID), plus other fields you need, such as date. Linked to the clients table on client ID and to the questions table on question ID.

When the client selects a check list, run code to add records to the latter table, with the client’s ID and the question ID for each question corresponding to the selected checklist ID. To fill in the check list, present these records in a continuous (sub)form. The thread starting at post 365875 describes a similar situation in a very different context.

Reply | Quote

thanks hans ,

Reply | Quote

thanks hans ,

Reply | Quote

I would create a separate table to hold the checklist ID and checklist name, and another table to hold the questions, with checklist ID, question ID and question text. These tables are linked by checklist ID. The first table will serve as the row source for a combo box from which the client can select a checklist.

Then, a table with client ID and checklist ID (composite primary key). A record in this table signifies that the client has selected a specific check list. Linked to the clients table on client ID and to the checklists table on checklist ID.

Finally, a table with client ID, question ID, result (Y/N), and perhaps also checklist ID (although that could also be derived from the question ID), plus other fields you need, such as date. Linked to the clients table on client ID and to the questions table on question ID.

When the client selects a check list, run code to add records to the latter table, with the client’s ID and the question ID for each question corresponding to the selected checklist ID. To fill in the check list, present these records in a continuous (sub)form. The thread starting at post 365875 describes a similar situation in a very different context.

Reply | Quote