This table provides a list of components for each business region. This information needs a data entry page. The components are placed together in the specified order to form a displayable page. Each component specifies an include file and/or text which forms part of the final content.
An business region component is accessed using its associated business region ID and sequence number.
Source romber_business_region_components_tbl.sql
create table romber_page.business_region_components ( business_region_id romber_member.relationship_id not null, page_component_include romber_base.generic_include not null, page_component_type_id romber_page.component_type_id not null );
Source romber_business_region_components_pk.sql
alter table romber_page.business_region_components add constraint romber_business_region_components_pk primary key ( business_region_id, page_component_type_id );
Source romber_business_region_components_fk1.sql
alter table romber_page.business_region_components add constraint romber_business_region_components_fk1 foreign key ( business_region_id ) references romber_base.business_regions ( business_region_id );
Source romber_business_region_components_fk2.sql
alter table romber_page.business_region_components add constraint romber_business_region_components_fk2 foreign key ( page_component_type_id ) references romber_page.component_types ( page_component_type_id );