Create SQL Table and relationship

I have 2 tables:
(1)Customer Table: Cust_Name, Cust_Address, Cust_age…….
Order Table: Cust_Name, Ord_Qty, Ord_Price……..

When I filled Cust_name in Customer Table, how to auto fill the Cust_Name in Order table as well?

(2)If I create Employee table with Employee_ID, Employee_Name_Address, and Skill. An employee may
have more than one skill. Each employee may work in one or more work centers. A
work center must have at least one employee working in that center; but may have
any number of employees.

How to link many skill to the Employee table, create another table or just put skill1, skill2 as attribute?
I already have work center table consist of workcenterID, workcenter_location…… to link many employees to 1 work center?
Who is Participating?
hafeezmcaConnect With a Mentor Commented:
Hope you are using Sql server/Ms access as the database. If not the structure will remain same but the datafield type will change.

Regarding your first question (Customer & Orders) create table with the following structure:

As you can get customer with same names so its not appropriate to have customer name as primary key. So I have added customerId as the Primary key.

Customer table: CustomerId Int Primary Key, Cust_Name nvarchar2(100), Cust_Address nvarchar2(100), Cust_age int …….

Order Table: CustomerId Int Foreign Key,  Ord_Qty int, Ord_Price decimal

You can create a form in any language.
The idea is to save the master record first ie. the customer table and get the customerId of the record inserted and then insert the data into Order table.

For your second query:

Create tables in the following structure:

Skills table: SkillId Int Primary Key, SkillName navarchar2
WorkCenter table: WorkCenterId Int Primary key, WorkCenterName nvarchar2
Employee table: Empid Int Primary Key, EmployeeName nvarchar2, Age int ....
EmployeeSkills table: EmpSkillId Int Primary Key, Empid Int Foreign Key, SkillId int Foreign Key
EmployeeWorkCenter table: EmpWorkcenterId Int Primary Key, Empid Int Foreign Key, WorkStationId int Foreign Key

This structure will help you to acheive your task.
You have to be good in programming to create master & details relationship pages.
Lee SavidgeCommented:
I think you need to do a lot of research on relational databases.

You need to understand designing relational databases, database normalisation and from what I can tell from your question, you need to understand how to write stored procedures to do the work for you.

With regards to the employee/skill relationship, my guess is that an employee can have many skills and a skill can belong to many people so this is a many to many relationship. As you cannot model this in a relational database directly you need to normalise it to give you this type of structure:

Employee --< EmployeeSkill >-- Skill

That way you have a skill table that links to an Employee via an EmployeeSkill table.
swpuiAuthor Commented:
so is the attached ER correct for relatioship between Employee & Skill?
swpuiAuthor Commented:
Let say I have sales territories for customers. Each customer may do
business in any number of these sales territories or may not do business in any
. A sales territory has one-to-many customers. The identifier for a sales
territory is Territory_ID and an attribute of a Territory_Name.

Territory table: TerritoryID Int Primary Key, TerritoryName nvarchar(50)
customer table: custID Int Primary Key, custName nvarchar(50)
custTerritory table: custterritoryID int Primary Key, TerritoryID Int FK, custID Int FK

ER would be:
Territory Tabel (1 to many) custTerritory table
customer table (0,1 or many) custTerritory table
How to draw relationship for "Each customer may do
business in any number of these sales territories or may not do business in any
swpuiAuthor Commented:
My last comments nobody seems to reply , anyway I had tried it and understand now
All Courses

From novice to tech pro — start learning today.