View Single Post
  #3  
Old November 9th, 2009, 02:07 PM posted to microsoft.public.access.tablesdbdesign
Fred
external usenet poster
 
Posts: 1,451
Default how to best structure this?

Hello Ivory Kitten,

Structure starts with a clear understanding of the entities that you want to
database, the relationships between them and a clear understanding of what
you want your database to accomplish.

Your post kind of hopped around and misxed terminology on your current
system ("Lists", "Spreadsheet" "Table" and so really didn't even clearly
describe your old system. Nor did you describe the real world
process/situation that you are trying to database, although, since you know
your business better than us, you probably mistakenly think that you have
done so my mentionioning all of those terminologies of your busines.


It appears clear that you have the following entities and have a mission to
database them:

- Linehaul suppliers
- Destinations

And so those probably should be tables. Include an autonumber Primary Key
in each of them.

After that it's unclear. A couple questions that might help you define it:

Besides storing lists of carriers and destinations, what do want this
database to accomplish?

Are there entities in that first list that you describe, and, if so, what
are they? Or is it just 2 blanks which a user fills in to trigger a
calculation, after which the data is not stored?

Hopes that helps a little