database structuring, sql insert multiple tables, help
I'm looking for some brainstorming on database configuration etc. Something isn't clicking. Here's what I'm looking at: I have a table for contacts, tblContacts - PK contactid, fields [FirstName], [MiddleName], [LastName]. I have a table for companies, tblCompanies - PK companyid, fields [CompanyName], [Address]. I have a table for managers of the companies, tblManagers - PK (managerid, FK [companyid] [contactid]). I have a table for directors of the companies, tblDirectors - PK (directorid, FK [companyid] [contactid]), fields [title].
Not every company will have Managers or Directors; however, any company can have several of either. Every contact will be associated with at least one company, but a contact can be a director of the same company more than once so long as the [title] differs.
I have a DetailsView control that displays the information from within the tblDirectors table for a selected Companyid - [title], [Firstname], [Middlename], [Lastname].
If a user would like to add a new Director to the currently selected Company, I would like them to be able to do so via Insert thru the DetailsView control. They would click Insert, enter the [title], [firstname], [middlename], [lastname] fields. The new director's name fields would need to be placed in the tblContacts table as a new record, but the Insert command would then need to discover/use the newly created contactid to Insert a new record into the tblDirectors table, along with the [title] and current Companyid so that this contact is associated with the selected Companyid as a Director. What sort of SQL statements am I looking at creating for this behavior? Is my database structure flawed from the get go? Something really just seems to be off and I can't place it :(
Is this making any sense? I feel like it would be beneficial to have you ask questions and I can then answer them to try and flesh this out. It's not adding up... please ask away.
Not every company will have Managers or Directors; however, any company can have several of either. Every contact will be associated with at least one company, but a contact can be a director of the same company more than once so long as the [title] differs.
I have a DetailsView control that displays the information from within the tblDirectors table for a selected Companyid - [title], [Firstname], [Middlename], [Lastname].
If a user would like to add a new Director to the currently selected Company, I would like them to be able to do so via Insert thru the DetailsView control. They would click Insert, enter the [title], [firstname], [middlename], [lastname] fields. The new director's name fields would need to be placed in the tblContacts table as a new record, but the Insert command would then need to discover/use the newly created contactid to Insert a new record into the tblDirectors table, along with the [title] and current Companyid so that this contact is associated with the selected Companyid as a Director. What sort of SQL statements am I looking at creating for this behavior? Is my database structure flawed from the get go? Something really just seems to be off and I can't place it :(
Is this making any sense? I feel like it would be beneficial to have you ask questions and I can then answer them to try and flesh this out. It's not adding up... please ask away.
ASKER
Thank you for the input! Problems I see though: each Contact can have multiple positions within the same Company. In addition, while a Manager is always just a Manager, a contact can twice be a Director of a company with two different titles, i.e. titleX and titleY.
John Smith can be Manager of MakeBelieve, Inc but also a Director titleX and Director titleY of PretendCo.
John Smith can be Manager of MakeBelieve, Inc but also a Director titleX and Director titleY of PretendCo.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
I like where you're going with this. I'm going to look into that right now but in the meantime I came up with this and wanted to put it on paper while it was fresh in my mind. Could you review this while I'm looking into your idea?
Pardon the crassness, but I think this illustrates what I'm thinking I need to accomplish to achieve the idea of creating a new Contact record and then using the newly created contactid. Does this make sense? Can I refine this code to work or is this not feasible
InsertCommand=
"DECLARE @contactid int, @err int
BEGIN TRAN
INSERT INTO [tblContacts] ([firstname], [middlename], [lastname]) VALUES (@firstname, @middlename, @lastname)
SET @err = @@error
IF @err = 0 BEGIN
SELECT @contactid = tblContacts.contactid WHERE tblContacts.lastname = @lastname AND tblContacts.firstname = @firstname
INSERT INTO [tblDirectors] ([companyid], [contactid], [title]) VALUES (@companyid, @contactid, @title)
SET @err = @@error
END
IF @err = 0
COMMIT TRAN
ELSE
ROLLBACK"
Pardon the crassness, but I think this illustrates what I'm thinking I need to accomplish to achieve the idea of creating a new Contact record and then using the newly created contactid. Does this make sense? Can I refine this code to work or is this not feasible
InsertCommand=
"DECLARE @contactid int, @err int
BEGIN TRAN
INSERT INTO [tblContacts] ([firstname], [middlename], [lastname]) VALUES (@firstname, @middlename, @lastname)
SET @err = @@error
IF @err = 0 BEGIN
SELECT @contactid = tblContacts.contactid WHERE tblContacts.lastname = @lastname AND tblContacts.firstname = @firstname
INSERT INTO [tblDirectors] ([companyid], [contactid], [title]) VALUES (@companyid, @contactid, @title)
SET @err = @@error
END
IF @err = 0
COMMIT TRAN
ELSE
ROLLBACK"
SQL 2008 has the hierarchy id
http://msdn.microsoft.com/en-us/library/bb677173.aspx
http://msdn.microsoft.com/en-us/library/bb677173.aspx
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
Even the manager has different positions you can still insert them in position two ways to do that if you know they will have just two roles then insert two columns for the position or if its way too many then have two tables first one will have all the position 2nd table can have the actual position I'd with userid and when you fetch them via department they will appear in their domain
ASKER
SCOPE_IDENTITY is working wonders for me at the moment, along with the addition of a tblCompanyContacts table. Thanks so much for the suggestions! Going to leave this question open as I'm sure I may have a few further questions.
1. Position Table (
ID int,
PositionName varchar(20)
)
ex data: (Manager, Director, Staff)
2. Company Table (usual company fields, eg. )
3. Contacts Table (ID, CompanyID, PositionID, Title, FirstName, LastName)