If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#1
|
|||
|
|||
Updating table
I need guidance on my database design:
I have a table that lists out several tasks in field 1, and includes about 7 other fields of information on the task. Some of these tasks are "Critical". If a task is critical, I need about 10 more fields with data on the task. Am I better off storing this info in 2 tables, or one? It is possible for a task that is currently not critical, to later become critical. I need a way to be able to easily keep track of and update this data. Any ideas? Thanks! |
#2
|
|||
|
|||
Updating table
On Mon, 8 Dec 2008 23:46:01 -0800, Mystified
wrote: If some of those fields are required if Critical=True, you would be better off with a second table with a 1:1 relation with the first one. If the fields are not required, or if there are sensible defaults in case Critical=False, I would KISS and keep everything in one table. -Tom. Microsoft Access MVP I need guidance on my database design: I have a table that lists out several tasks in field 1, and includes about 7 other fields of information on the task. Some of these tasks are "Critical". If a task is critical, I need about 10 more fields with data on the task. Am I better off storing this info in 2 tables, or one? It is possible for a task that is currently not critical, to later become critical. I need a way to be able to easily keep track of and update this data. Any ideas? Thanks! |
#3
|
|||
|
|||
Updating table
Thanks Tom.
I'm leaning toward 2 tables, since fields when critical=true are required. Each time I add a new task to Table one, is there a way for this to be automatically added to Table 2? I have a query that launches from a button the form, so if a user adds a new task, I am wondering if they will have to add it to both tables, or if adding it to one table will be enough. Hope that makes sense. "Tom van Stiphout" wrote: On Mon, 8 Dec 2008 23:46:01 -0800, Mystified wrote: If some of those fields are required if Critical=True, you would be better off with a second table with a 1:1 relation with the first one. If the fields are not required, or if there are sensible defaults in case Critical=False, I would KISS and keep everything in one table. -Tom. Microsoft Access MVP I need guidance on my database design: I have a table that lists out several tasks in field 1, and includes about 7 other fields of information on the task. Some of these tasks are "Critical". If a task is critical, I need about 10 more fields with data on the task. Am I better off storing this info in 2 tables, or one? It is possible for a task that is currently not critical, to later become critical. I need a way to be able to easily keep track of and update this data. Any ideas? Thanks! |
#4
|
|||
|
|||
Updating table
On Tue, 9 Dec 2008 10:47:03 -0800, Mystified
wrote: No. An insert query acts on a single table. You will need two insert queries, and insert the one side before the many side. -Tom. Microsoft Access MVP Thanks Tom. I'm leaning toward 2 tables, since fields when critical=true are required. Each time I add a new task to Table one, is there a way for this to be automatically added to Table 2? I have a query that launches from a button the form, so if a user adds a new task, I am wondering if they will have to add it to both tables, or if adding it to one table will be enough. Hope that makes sense. "Tom van Stiphout" wrote: On Mon, 8 Dec 2008 23:46:01 -0800, Mystified wrote: If some of those fields are required if Critical=True, you would be better off with a second table with a 1:1 relation with the first one. If the fields are not required, or if there are sensible defaults in case Critical=False, I would KISS and keep everything in one table. -Tom. Microsoft Access MVP I need guidance on my database design: I have a table that lists out several tasks in field 1, and includes about 7 other fields of information on the task. Some of these tasks are "Critical". If a task is critical, I need about 10 more fields with data on the task. Am I better off storing this info in 2 tables, or one? It is possible for a task that is currently not critical, to later become critical. I need a way to be able to easily keep track of and update this data. Any ideas? Thanks! |
Thread Tools | |
Display Modes | |
|
|