[AccessD] Table Structure Ideas

Hi Charlotte,

Yes, I am at that stage and coming to a similar conclusion as you. My
concern is the Polarised Light Microscopy being displayed horizontally
rather than vertically, which makes it a lot more complicated. I've just
found out that there could be more than samples A, B, C and D, so that
complicates it more.

Is there a way to display a continuous form horizontally rather than
vertically?

Thanks

Vlado

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Charlotte Foust
Sent: Thursday, 11 September 2014 4:44 AM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Table Structure Ideas

You need a table for samples with a field that allows you to determine the
order.  Then you might use a table for Fibers Morphology and another for
Polarized Light Microscopy, each with the fields needed for the information
that applies.  Each of those tables would be child tables to the main Sample
table, which would contain any other information collected for a sample.
The Sample PK would be a FK in each of the child tables.

That would allow you to present the information in a variety of layouts
without straining yourself.  This assumes a one-to-one relationship between
the tables but could allow for the addition of multiple results if you added
a unique key to each child table as PK and  allowed duplicates of the parent
key.  If they wanted to add different kinds of results, you would just add
another table.

Charlotte

On Tue, Sep 9, 2014 at 11:11 PM, ACTEBS <actebs at actebs.com.au> wrote:

> Hi Everyone,
>
>
>
> Got a complex form that we're turning into a DB and having difficulty 
> coming up with a good table structure to suit the form and the way the 
> data is collected and input.
>
>
>
> They want the Access DB to mirror the form. You can see the form here:
>
>
>
> http://download.actebs.com.au/FormDoc.jpg
>
>
>
> As you can see by the example image above the sample are marked as A, 
> B, C, and D, but sometimes they display it vertically and other 
> horizontally, which is confusing the hell out of me. Any idea on how 
> best to design the table structure so the data is easy to work with down
the track?
>
>
>
> Any ideas most welcome.
>
>
>
> Thanks in advance.
>
>
>
> Vlado
>
>
>
>
>
> --
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
>
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com