|
| 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
July 30th, 2009, 06:27 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
too many tables?
I am working on creating a new database to log in samples and the track the
results of tests (25+) on the samples. Any sample can have any or all of the tests performed on it so I will need to record up to 25 test results for any one sample. I also want to record the date the test was run and who ran the test. I have set up the database so that there is a log-in table to record the information about the sample and then I have a table for each of the tests. So far there are about 25 tests so I have 25 test tables. This seems like a lot of unnecessary tables that I could combine somehow. Any vision on a better way to set this up would be greatly appreciated! Thanks Mike 
|
|
#2
July 30th, 2009, 06:54 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
too many tables?
You should have only one table for each kind of data. You wouldn't have a
table for all the Smith's, another for Jones', etc., would you. Combine at the tests into one table. You may need to split out repeating day to other tables. Also remember to go down and not across with the data. You don't want this: Test1 Test2 Test2 and so on across. Rather you something like: Tests Results 1 Pass 2 Fail -- Jerry Whittle, Microsoft Access MVP Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder. "Mike" wrote: I am working on creating a new database to log in samples and the track the results of tests (25+) on the samples. Any sample can have any or all of the tests performed on it so I will need to record up to 25 test results for any one sample. I also want to record the date the test was run and who ran the test. I have set up the database so that there is a log-in table to record the information about the sample and then I have a table for each of the tests. So far there are about 25 tests so I have 25 test tables. This seems like a lot of unnecessary tables that I could combine somehow. Any vision on a better way to set this up would be greatly appreciated! Thanks Mike
|
|
#3
July 30th, 2009, 10:01 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
too many tables?
On Thu, 30 Jul 2009 10:27:02 -0700, Mike
wrote: I am working on creating a new database to log in samples and the track the results of tests (25+) on the samples. Any sample can have any or all of the tests performed on it so I will need to record up to 25 test results for any one sample. I also want to record the date the test was run and who ran the test. I have set up the database so that there is a log-in table to record the information about the sample and then I have a table for each of the tests. So far there are about 25 tests so I have 25 test tables. This seems like a lot of unnecessary tables that I could combine somehow. Any vision on a better way to set this up would be greatly appreciated! Thanks Mike You need four tables, not 26. Samples SampleID primary key log information about the sample, e.g. source, sample date, etc. Tests TestNo primary key Description Testers TesterID primary key LastName FirstName other personal identification Results SampleID link to Samples TestNo link to Tests TestDate TesterID TestResult -- John W. Vinson [MVP]
|
|
#4
July 31st, 2009, 12:34 PM
posted to microsoft.public.access.tablesdbdesign
|
|||
|
|||
|
too many tables?
Thanks for all the hilp I think I can see the light now!
"John W. Vinson" wrote: On Thu, 30 Jul 2009 10:27:02 -0700, Mike wrote: I am working on creating a new database to log in samples and the track the results of tests (25+) on the samples. Any sample can have any or all of the tests performed on it so I will need to record up to 25 test results for any one sample. I also want to record the date the test was run and who ran the test. I have set up the database so that there is a log-in table to record the information about the sample and then I have a table for each of the tests. So far there are about 25 tests so I have 25 test tables. This seems like a lot of unnecessary tables that I could combine somehow. Any vision on a better way to set this up would be greatly appreciated! Thanks Mike You need four tables, not 26. Samples SampleID primary key log information about the sample, e.g. source, sample date, etc. Tests TestNo primary key Description Testers TesterID primary key LastName FirstName other personal identification Results SampleID link to Samples TestNo link to Tests TestDate TesterID TestResult -- John W. Vinson [MVP]
|
| Thread Tools | |
| Display Modes | |
|
|
Linear Mode
