Re: Invalid Variant Operation
From: Brian Bushay TeamB (BBushay_at_Nmpls.com)
Date: 09/24/04
- Next message: Brian Bushay TeamB: "Re: Getting Parameters at runtime"
- Previous message: Brian Hollister: "Re: Invalid Variant Operation"
- In reply to: Matthew Pascoe: "Re: Invalid Variant Operation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 24 Sep 2004 09:13:08 -0500
>Just a quick question on the return paramter bing null.
>
>I am trying to figure out how to check for a null value so I don't create an
>error.
>
>The only way I seem to be able to access the value is
>'proc1.Parameters.ParamByName('@RETURN_VALUE').Value'
>
>It won't let me use AsInteger, AsString, or the IsNull option instead of the
>'Value' property?
You already got the correct answer from Brian Holister on this one.
I just want to add that you really should try to figure out why you are getting
the deadlock and if there is another way to write your stored procedure to avoid
it. Deadlocks use up a lot of resources and if you are adding more uses you are
likely to get them more frequently.
Brian
-- Brian Bushay (TeamB) Bbushay@NMPLS.com
- Next message: Brian Bushay TeamB: "Re: Getting Parameters at runtime"
- Previous message: Brian Hollister: "Re: Invalid Variant Operation"
- In reply to: Matthew Pascoe: "Re: Invalid Variant Operation"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
