September 23, 2008 at 6:22 pm
Hey guys,
So i have a stored procedure that has a few statements, etc.
When I try to save my stored procedure I get:
Implicit conversion from data type varchar to varbinary is not allowed. Use the CONVERT function to run this query.
those are the lines that i'm having a problem with
CREATE PROCEDURE [dbo].[usp_procedure1]
-- Add the parameters for the stored procedure here
@IDbigint = 0,
@value1 varchar(16) = NULL
AS
BEGIN
SET NOCOUNT ON;
DECLARE @eValue varbinary(80);
EXEC dbo.eProcedure @value1,@eValue OUTPUT;
UPDATE [table1] SET
column1=@eValue
WHERE condition=Blah;
Anybody has an idea on this?
Thanks!
September 23, 2008 at 6:41 pm
Well either the second parameter of the dbo.eProcedure stored procedure is of type VARCHAR, or column1 of table1 is of type VARCHAR.
Perhaps make sure @eValue is the same type as the output parameter of dbo.eProcedure, and cast it to the same type as the column that you're trying to set.
September 23, 2008 at 6:43 pm
Hi there,
I think your problem is here
EXEC dbo.eProcedure @value1,@eValue OUTPUT
Can you post the code that you used for this sproc. Its either the parameters for @Value in this sproc is not VARBINARY or the value given to it by the sproc is VARCHAR... It depends on the sproc you called
_____________________________________________
[font="Comic Sans MS"]Quatrei Quorizawa[/font]
:):D:P;):w00t::cool::hehe:
MABUHAY PHILIPPINES!
September 23, 2008 at 8:48 pm
Column1 of table1 is indeed of varbinary type.
dbo.eProcedure as the following definition:
CREATE PROCEDURE [dbo].[eProcedure]
-- Add the parameters for the stored procedure here
@cT varchar(MAX) = NULL,
@et varbinary(MAX) OUTPUT
AS
BEGIN
....
as @value1 is of varchar type... and @eValue is of type varbinary, i would expect no problems?
Let me recall:
EXEC dbo.eProcedure @value1,@eValue OUTPUT
September 24, 2008 at 12:01 pm
Bump... Anyone?
This is very weird haha i'm sure it's something really stupid, i just can't see it :S
September 24, 2008 at 3:09 pm
Hey,
Thanks for everyone's input, problem fixed.. my declaration for a variable was bogus, i thought i had varbinary, but it was varchar
September 27, 2008 at 7:47 pm
Heh... thanks for posting your solution. Sometimes the problem just boils down to "must look eye."
--Jeff Moden
Change is inevitable... Change for the better is not.
September 27, 2008 at 9:49 pm
Jeff Moden (9/27/2008)
Heh... thanks for posting your solution. Sometimes the problem just boils down to "must look eye."
Any more references like these and you're going to have to start kicking royalty fees over to Pat Morita:)
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
September 28, 2008 at 6:40 pm
Matt Miller (9/27/2008)
Jeff Moden (9/27/2008)
Heh... thanks for posting your solution. Sometimes the problem just boils down to "must look eye."Any more references like these and you're going to have to start kicking royalty fees over to Pat Morita:)
Heh... other way around... I taught Pat everything he knows. I used to be able to stand on a post, too... but then we got a divorce. :hehe:
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply
This website stores cookies on your computer.
These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.
To find out more about the cookies we use, see our Privacy Policy