Table structure

[kenny.love]

I work in a lab and I have have to create a database for the purpose of
sample storage. Sample are stored in containerswith 100 locations
(A1-A10 B1-B10 etc). Samples have unique numbers. I can't get my head
around how the tables would be structured.

How would it work without having seperate tables for each container.
Would each location be in the same table as container ID??? I'm
stuck...

Regards,

Kenny Love

 

[John Vinson]

I work in a lab and I have have to create a database for the purpose of
sample storage. Sample are stored in containerswith 100 locations
(A1-A10 B1-B10 etc). Samples have unique numbers. I can't get my head
around how the tables would be structured.

How would it work without having seperate tables for each container.
Would each location be in the same table as container ID??? I'm
stuck...

Your storage location should be defined by THREE fields - ContainerID,
Row (A - J), Col (1-10). You might have a table

StorageLocations
ContainerID Long Integer <Primary Key>
Row Text(1) <Primary Key>
Col Integer <Primary Key>
SampleID <link to the table of things stored>

Note that a Primary Key can consist of up to ten fields, you don't
need to concatenate into one.

You'll probably want a table of Containers to indicate where each
container itself is located, and a table of Samples with the
information about the nature and source of the sample.


John W. Vinson[MVP]

 

[kenny.love]

Many thanks John. I cant believe I didn't think of splitting up the
location into row and column!!! Many Thanks again!!

 

[John Vinson]

Many thanks John. I cant believe I didn't think of splitting up the
location into row and column!!! Many Thanks again!!

One of my first relational database projects (ca. 1980) was to index
samples stored in microtiter plates (A1 - H12, different sample in
each).

John W. Vinson[MVP]