[AccessD] Table Structure Ideas

Gustav Brock gustav at cactus.dk
Wed Sep 10 02:38:36 CDT 2014


Hi Vlado

I would use a parent table and four child tables, one for each section.
Further, I would suggest a tabbed form for data entry; the existing form is not suitable for screen usage.

/gustav

-----Oprindelig meddelelse-----
Fra: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] På vegne af ACTEBS
Sendt: 10. september 2014 08:27
Til: 'Access Developers discussion and problem solving'
Emne: Re: [AccessD] Table Structure Ideas

Hi Darryl,

Yes, sorry I should have made that clearer. I'm basically after ideas for the table structure. Forget about the user interface, I can manipulate it to suit. I just can't come up with an elegant solution for the tables.

Thanks

Vlado

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Darryl Collins
Sent: Wednesday, 10 September 2014 4:21 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Table Structure Ideas

Hi Vlado,

By the "Want the DB to mirror the form" requirement, I assume you mean for
the data entry requirement.   How you set up the underlying table structure
should be very different.
Is that your understanding as well?

Cheers
Darryl

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of ACTEBS
Sent: Wednesday, 10 September 2014 4:11 PM
To: access group
Subject: [AccessD] Table Structure Ideas

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 



More information about the AccessD mailing list