August 9, 2010 at 6:19 pm
create procedure edifyp
(
@firstname varchar(50),
@lastname varchar(50),
@Username varchar(50),
@password varchar(50),
@cpassword varchar(50)
)
as insert into esignup
(
[firstname],
[lastname],
[username],
[password],
[cpassword]
)
values
(
@firstname ,
@lastname ,
@Username ,
@password ,
@cpassword
)
August 9, 2010 at 7:45 pm
I don't see an issue with it. Why do you think there is one?
Wayne
Microsoft Certified Master: SQL Server 2008
Author - SQL Server T-SQL Recipes
August 10, 2010 at 6:27 am
Looks OK to me. Are you getting an error? If so, what is it?
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
August 10, 2010 at 6:35 am
Perhaps...
The table doesn't exist?
You are storing passwords unencrypted?
If that is the standard of formatting in the database, your formatting standards could be improved.
Come on, give us a clue. Is this for a pub quiz?
August 11, 2010 at 7:04 am
You're not specifying the owner/schema for the stored procedure and/or the table you're inserting into? You're trying to insert NULL values into columns that don't allow NULLs? The moon isn't in the seventh house?
Wow, the possibilities are endless!
August 11, 2010 at 7:16 am
Inconsistent casing - do I not like that.
Jupiter isn't aligned with Mars, this isn't the dawning of the age of Aquarius...
August 12, 2010 at 12:24 am
Hey i don't see any issue with the procedure. If is their any problem check your table once again
August 13, 2010 at 2:30 pm
The procedure is syntatically correct. The mistake is in not telling us what error you are receiving.:unsure:
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply