Re: Table acting as a relation table

I am going to rephrase my question:

T_HOSPITAL <-------------- T_HOSPITAL_CLINIC <-------------> T_CLINIC

  HOSP_CODE                    HOSP_CODE
CLINIC_CODE
                                          CLINIC_CODE

With my asssociation table I can define which clinic belongs to which hospital. Someone told me that such table cannot have the only two field HOSP_CODE, CLINIC_CODE, but some other "key" field should be there. Quote "a table with no key to identify each row should not be modeled".

Obviously my table will work as is. Is there however a rule I am enfringing ? Received on Tue Apr 10 2007 - 17:32:01 CDT