Re: Best Practice for tables?
- From: "Arvin Meyer [MVP]" <a@xxxxx>
- Date: Mon, 20 Aug 2007 10:14:36 -0400
It sounds right if it's that simple. Instead of using the actual text from
the 3 tables, use the ID or Primary Key value.The tblRoutingSystem should
contain:
CountryID
DispatchMethodID
SupplierID
Now if the Supplier decides to sell the company or change its name, you
simply change it once in the Supplier table, and it propogates throughout
the database from the queries used to display the SupplierName.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com
"Kamitsukenu" <Kamitsukenu@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:72266BF7-C758-4089-A0BD-71AE9551859A@xxxxxxxxxxxxxxxx
Hi there,
The company I work for mail items dependent on destination, weight and
speed
of delivery.
I'm trying to make a system in Access, and during setting up all the
tables,
I'm getting myself more and more confused.
I have the following tables;
(tblCountry) - holds the Country names
(tblDispatchMethod) - the service the item is sent by
(tblSupplier) - who the item is mailed by
Now, as dispatch of items are dependent on the weight, I have another
table
which combines all the above information.
TblRoutingSystem contains
'CountryName' which refers to 'tblCountry'
'DispatchMethod' which refers to 'tblDispatchMethod'
'NameofSupplier' which refers to 'tblSupplier'
'WeightBandStart' and 'WeightBandEnd' which refer to (surprise, surprise)
the start and end of the weight bands for deciding the correct supplier
for
mailing.
Does this sound about right, or should I be split them out further or
should
I be merging more stuff together.
in fact, can someone go through the pros and cons of creating more tables
to
suit the data?
Thanks
K
.
- Prev by Date: Re: Upgrade Access 2000 to 2003
- Next by Date: Re: How to capture last used date/time
- Previous by thread: Re: Upgrade Access 2000 to 2003
- Next by thread: Re: Best Practice for tables?
- Index(es):
Relevant Pages
|