Log in

No account? Create an account

Previous Entry | Next Entry

Having to build a relational database in MS Access.

Never worked with relational databases or Access before.

I need reports to generate a history of build numbers on a particular system, and the tests passed within those build numbers. The database needs to retain the history even as new build numbers are added.

My brain hurts.



( 10 comments — Leave a comment )
Jan. 8th, 2008 09:31 pm (UTC)
i don't know anything about that except i am digging the word
Jan. 8th, 2008 09:44 pm (UTC)
Have one table in your DB contain only the build numbers, use the build number as the Primary Key.

That table will be the one that all the others refer too.
Jan. 8th, 2008 09:47 pm (UTC)
Each build number has a certain number of validation tests it has to pass as well. Do I put all of that in one table, or create a new table with just the tests?


build 58 has tests A, B, C
build 59 has tests A, B, C
build 61 has tests A, B, C, and D

all the tests are pass/fail.

so fer instance,

system 07-511 has build 58, passed A and C
system 07-512 has build 61, passed A and D
system 07-513 had build 58, passed A B C, now has build 61, passed A, B, C, D

Edited at 2008-01-08 09:50 pm (UTC)
Jan. 8th, 2008 09:50 pm (UTC)
hence the term "test"
all the tests are pass/fail.

are not all tests like that?

Jan. 8th, 2008 10:33 pm (UTC)
Re: hence the term "test"
Not necessarily. In the case of software validation, yes-- it's a part of the formal design, but something like a test in school, you may get a percentage or a letter grade.
Jan. 8th, 2008 09:56 pm (UTC)
Well what I would do is this:

Table A contains Build # and % passed, the build number is a required and key field.

Table B Contains a column for test A-D (this will be a Binary Pass Fail, but not required ). The Primary key could be something like Test Sequence. The foreign keys for this table would be the Build #.

Thus you have a one to many relationship where one build would have many tests that could be run

make sense?
Jan. 8th, 2008 10:35 pm (UTC)
I think so. It's like objects and instances: you define the object (the table) once, but you may have many instances of that object.

I'm just trying to anticipate what the PM is going to want to ask for in reports. So far I've been pretty good at it, but this is new.
Jan. 9th, 2008 01:38 am (UTC)
Yay lookup tables! :D

PS: I have a book on programming some application stuff in Access. Yours for the taking, if'n you want it.
Jan. 9th, 2008 02:33 am (UTC)
A book would be gooood, yes thanks!
Jan. 9th, 2008 01:49 am (UTC)
Huh. Oddly enough, today at work I finished a lame d.i.y. training course on Microsoft Office which included Access. I'll probably never actually use that software.

Edited at 2008-01-09 01:49 am (UTC)
( 10 comments — Leave a comment )

Latest Month

April 2012


Powered by LiveJournal.com
Designed by Tiffany Chow