Re: Best Practice for tables?

No one has yet mentioned form and report names. I prefix all form names with
Frm and prefix all subreport names with SFrm. I get two distinct advantages
from this. First, when I look at the forms database window, all form names
appear first and all subform names are grouped separately from form names.
Second, it helps to catch errors when referencing forms and subforms..

The way I name reports and subreports is similar to the way I name forms and
subforms. I prefix reports with Rpt and I prefix subreports with SRpt. The
advantages for reports are the same as the advantages for forms.

PC Data***
Providing Customers A Resource For Help With Access, Excel And Word
Applications
resource@xxxxxxxxxxxxxxx



"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




.