Re: Separate PK in Jxn Tbl?

-CELKO- <jcelko212_at_earthlink.net> wrote:

>>> I always use an autonumber PK and a unique index set on the two FK fields [sic]. Why? No particular good reason. One of my database rules is that all tables have an autonumber primary key [sic]. <<
>
>You add redundancy to a schema and never thought about it?

I have and I'm quite comfortable with it.

>If you had
>gone thru the Normalization process, this would stick out as a
>fundamental design error immediately. You have not been writing SQL;
>you are faking a sequential file system in SQL and even say "field"
>instead of "column" -- huge conceptual and implementation differences!

Ok.

>> Now if I was to have a child table [sic: that terms comes from Network DBs; did you used to program in IMS?] from the junction table [sic: did you mean a table that models a relationship among many entities? Or a multi-way pointer structure as in an Network DB?] then I would absolutely use a autonumber primary key [sic: it cannot be a key by definition] for ease of use when designing queries, forms and reports. <<

Never woked in IMS or Network DBs. These are common terminology in the Access world so that's what I use.

>I hope that you are not designing forms and reports in the database.

You've never used Access then?

Tony

-- 
Tony Toews, Microsoft Access MVP
   Please respond only in the newsgroups so that others can 
read the entire thread of messages.
   Microsoft Access Links, Hints, Tips & Accounting Systems at 
http://www.granite.ab.ca/accsmstr.htm
   Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/