Use of normalised information

[Ulto]

I have a table with company information, where the uniqe key is organisation
number, which i have normalised on company code.

In that new table on company code, i have givin each code a ranking(number)
after how important that code is for me (e.g. stockcompany(SC) got 1, where i
singleowner company(SOC) got a higher number)

I now want a tabel where it is the phonenumber that is the uniqe key, and
since the same phonenumber can have "many" differents organisation numbers,
then i want the right companycode attached to the phonenumber (e.g. SC if one
of the companies is a stock based)

The question is then, how do i secure that i get the right company code on a
phone number?

I like to put these information in another tabel, and from there update my
tabel where the phonenumber is key.

Hope that i have made my question clear, and that one of you can help me

 

[Jerry Whittle]

Where I live phone numbers are frequently changed especially area codes.
Unless you know that a phone number will NEVER be changed, I would not use a
phone number as a primary key.

 

[Ulto]

I am making list for our telesales department, so the phone number only needs
to be "valid" a month or so, and it is not unusual that a surtain phone
number covers up to 10 uniqe organisations number, so when i make phone
number the key, then will i advoid the company beíng called by us 10 times.
But that means that i need to "sum" attribute on these ten companies, which
is what my current problem is about.

"Jerry Whittle" skrev: