Viewing 10 posts - 1 through 11 (of 11 total)
This particular system only has three WBS levels:
Project WBS1
Phase WBS2
Task WBS3
When the system was implemented, the business development team decided that they only wanted to use WBS1 level, a...
December 14, 2009 at 9:23 pm
Thank you for all of your help! 🙂
Here it is:
CREATE PROCEDURE dbo.insert_AssociatedContracts
@WBS1 varchar(30)
AS
INSERT INTO [dbo].[Projects_AssociatedContracts] (
...
December 14, 2009 at 5:26 pm
Hall of Fammer,
Yours works beautifully. I see also the message regarding the insert and select values. I want the first and last name listed in Employee table...
December 14, 2009 at 4:26 pm
Modified:
With the following errors:
Msg 102, Level 15, State 1, Procedure insert_AssociatedContracts, Line 3
Incorrect syntax near '@WBS2'.
Msg 137, Level 15, State 2, Procedure insert_AssociatedContracts, Line 34
Must declare the scalar variable "@WBS1".
I...
December 14, 2009 at 4:15 pm
I meant to say that the PR table has over 40 columns.
December 14, 2009 at 3:43 pm
The unique identifier will be WBS1. All specified data for each row is uniquely identified as belonging to the same WBS1. I'm pulling this specific set of data...
December 14, 2009 at 3:24 pm
I think I understand. So I modified the code accordingly.
CREATE PROCEDURE dbo.insert_AssociatedContracts
@WBS1 varchar(30)
@WBS2 varchar(7)
@WBS3 varchar (7)
@Name varchar (40)
@ProjectMgr varchar (20)
@StartDate datetime
@EndDate datetime
@Firmcost decimal(19,4)
AS
INSERT INTO [dbo].[Projects_AssociatedContracts] (
...
December 14, 2009 at 3:13 pm
I'm actually using all input parameters. I'm trying to make sure that all jobs (WBS2) and associated data
[WBS3],
...
December 14, 2009 at 2:48 pm
Thank you for your quick response. I really appreciate it.
Yes, I was getting errors.
Now I get one error:
Msg 137, Level 15, State 2, Line 23
Must declare the scalar variable...
December 14, 2009 at 12:19 pm
Viewing 10 posts - 1 through 11 (of 11 total)