Hi all
I looked to make sure I shouldn't be posting this elsewhere, and this seems to be the right place, I think.
I can't find anywhere that really puts a direct answer to my question, though it may be somewhat down to my lack of knowledge. Here is my situation:
I am creating a system that will use Access for its database. The system will be used to send communications to other teams, and will provide them with:
In the background, I refer to each of these "levels" as "level1" (first bullet-point), "level2" and "level3".
As the user will only ever choose from the options they are presented with (as opposed to free-type each time), how the hell do I go about creating tables for this?
[Added in edit to add detail:] With these level1, 2, 3 choices being prescribed (they must choose what they are presented), when it comes to uploading this data to the Access database, should they have their own tables (level1, 2, 3) or should there be a table for every potential list that can come up based on a user's choices along the way?
This is all in an effort to create an efficient database, and keep it 'normalized'.
It's worth stating that the database also collects unique data such as relevant order numbers, account numbers etc., all of which is sitting in its own table at the moment. However, from a reporting perspective, I would like to be able to view everything, including what choices they selected along the way, as well as the unique info mentioned.
The chances are, I'm missing something conceptual, but I could do with a steer even if that's the case.
Thanks in advance.
Jon
I looked to make sure I shouldn't be posting this elsewhere, and this seems to be the right place, I think.
I can't find anywhere that really puts a direct answer to my question, though it may be somewhat down to my lack of knowledge. Here is my situation:
I am creating a system that will use Access for its database. The system will be used to send communications to other teams, and will provide them with:
- Who they wish to send a communication to (team, individual etc.)
- Based on their initial choice, what type of query they wish to submit (e.g. if 'Team' were selected: feedback, complaint etc.)
- Based on the previous choice, more specific options. So, if complaint were chosen, the user will then see a list of choices specific to complaints (e.g. service, departmental etc.)
In the background, I refer to each of these "levels" as "level1" (first bullet-point), "level2" and "level3".
As the user will only ever choose from the options they are presented with (as opposed to free-type each time), how the hell do I go about creating tables for this?
[Added in edit to add detail:] With these level1, 2, 3 choices being prescribed (they must choose what they are presented), when it comes to uploading this data to the Access database, should they have their own tables (level1, 2, 3) or should there be a table for every potential list that can come up based on a user's choices along the way?
This is all in an effort to create an efficient database, and keep it 'normalized'.
It's worth stating that the database also collects unique data such as relevant order numbers, account numbers etc., all of which is sitting in its own table at the moment. However, from a reporting perspective, I would like to be able to view everything, including what choices they selected along the way, as well as the unique info mentioned.
The chances are, I'm missing something conceptual, but I could do with a steer even if that's the case.
Thanks in advance.
Jon
Last edited: