Access 2003, autonumbers

Thanks Tina,

I was thinking about the tblGRADES before, but thinking about it now, the
grade section for the tblCOINS will only be a number. Linked to the
tblGRADES, less space in the tblCOINS.

For the grading, I have 15 grading specs per coin. (poor), (fair), (good),
(fine), (very fine), (extremely fine) are just a few. Never the less I want
to thankyou for your assistance.

Sincerely,

Dave Hubbard

"tina" wrote:

your 3rd normal form table design looks fine to me. the only note i might
include: if you have a standard set of "grades" that you apply to all coins
(i have no idea what this would be - excellent condition, good condition,
poor condition? whatever), then you could also include a

tblGRADES
GradeID -- PK
GradeName

then instead of the Grading field in tblCOINS, use the GradeID field as a
foreign key to tblGRADES.

since you know what "grading" is (and i don't), you'll need to decide if the
above suggestion is appropriate for your database or not.

hth


"Dave Hubbard" ( donotspam ) wrote in message
...
So Chris or Tina if I'm trying to Normalize my database my tables should
look like this?

If my table in 1NF is:
tblFIRST
CountryName
ContinentName
CoinID# -- PK
Denomination
Grading
ObverseDevice (picture heads side)
ReverseDevice (picture tails side)
Inscription
Motto

Then my tables in 3NF would be:
tblCONTINENT
ContinentName
ContinentID# -- PK
--------------------------
tblCOUNTRY
CountryName
CountryID# -- PK
ContinentID# -- FK to tblCONTINENT
--------------------------
tblCOINS
CoinID# -- PK
CountryID# -- FK to tblCOUNTRY
Denomination
Grading
ObverseDevice (picture heads side)
ReverseDevice (picture tails side)
Inscription
Motto
--------------------------

This way I won't have to link by the country or continent names, but by
either the CountryID# or the ContinentID#. I think this should help
minimize
the space needed to run my application.
Understanding this ACCESS 2003 is really confusing, but I'm not afraid to
try anything.

Much appreciation with any assistance,

Dave Hubbard

you're welcome


"Dave Hubbard" ( donotspam ) wrote in message
...
Thanks Tina,

I was thinking about the tblGRADES before, but thinking about it now, the
grade section for the tblCOINS will only be a number. Linked to the
tblGRADES, less space in the tblCOINS.

For the grading, I have 15 grading specs per coin. (poor), (fair),
(good),
(fine), (very fine), (extremely fine) are just a few. Never the less I
want
to thankyou for your assistance.

Sincerely,

Dave Hubbard

"tina" wrote:

your 3rd normal form table design looks fine to me. the only note i
might
include: if you have a standard set of "grades" that you apply to all
coins
(i have no idea what this would be - excellent condition, good
condition,
poor condition? whatever), then you could also include a

tblGRADES
GradeID -- PK
GradeName

then instead of the Grading field in tblCOINS, use the GradeID field as
a
foreign key to tblGRADES.

since you know what "grading" is (and i don't), you'll need to decide if
the
above suggestion is appropriate for your database or not.

hth


"Dave Hubbard" ( donotspam ) wrote in
message
...
So Chris or Tina if I'm trying to Normalize my database my tables
should
look like this?

If my table in 1NF is:
tblFIRST
CountryName
ContinentName
CoinID# -- PK
Denomination
Grading
ObverseDevice (picture heads side)
ReverseDevice (picture tails side)
Inscription
Motto

Then my tables in 3NF would be:
tblCONTINENT
ContinentName
ContinentID# -- PK
--------------------------
tblCOUNTRY
CountryName
CountryID# -- PK
ContinentID# -- FK to tblCONTINENT
--------------------------
tblCOINS
CoinID# -- PK
CountryID# -- FK to tblCOUNTRY
Denomination
Grading
ObverseDevice (picture heads side)
ReverseDevice (picture tails side)
Inscription
Motto
--------------------------

This way I won't have to link by the country or continent names, but
by
either the CountryID# or the ContinentID#. I think this should help
minimize
the space needed to run my application.
Understanding this ACCESS 2003 is really confusing, but I'm not afraid
to
try anything.

Much appreciation with any assistance,

Dave Hubbard