Re: Hierarchy/Many to Many/Temporal data - MIND BENDER

They are unique in the simplified example that I posted.

In the future if there is a date in that table then you will be able to have the same skill assigned to the same experience twice. Each with a different date.

With a surrogate key, the programming is easy:

example asp script using surrogate key:
exp.asp?action=edit&key=45

I just use "select * from company where companiID = 45" in the above script.

Or an application can pass a value to a form property in Access or VB.

Example:
myform.key=45

What do you propose would be passed to the routine for editing the data after using multiple fields as a key?

Darcy

"andrewst" <member14183_at_dbforums.com> wrote in message news:3255147.1061199145_at_dbforums.com...
>
> Originally posted by Me
>
> > I like surrogate keys...
>
> >
>
> You certainly do! What is wrong with using (ExperienceID,SkillID) as
> the primary key for ExperienceSkill rather than adding the surrogate
> ExperienceSkillID? You surely want them to be unique anyway.
>
>
> --
> Posted via http://dbforums.com
Received on Mon Aug 18 2003 - 14:17:56 CEST