Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 11 to 13 of 13 total |
Procedure and NULL parameters... |
Wed, Aug 4 2010 6:57 AM | Permanent Link |
Uli Becker | Charles,
> TIntegerField.Value must return a Longint. When it encounters a null it > returns 0. So VarIsNull(SourceTableMyInteger.Value) = VarIsNull(0) = > false. > > VarIsNull(SourceTableMyInteger.AsVariant) would possibly do what you > wanted. Thanks for the explanation. That makes sense. Uli |
Wed, Aug 4 2010 6:58 AM | Permanent Link |
Uli Becker | Roy,
> Me neither but I use .IsNull out of habit so I wouldn't encounter that. Charles explained it well. > My understanding is that parameters are persistent so you'll need to set each time they change. Yes, that's what I guessed. Uli |
Thu, Aug 5 2010 3:26 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Uli,
<< Thank you. That works indeed. (Though I don't understand why VarIsNull doesn't work). >> Charles is correct - Value always returns an Integer value, regardless of the NULL state. << One more question: if I execute the procedure several times with different parameters: have I to clear the parameters that I want to pass as NULL like this: >> Yes, you need to Clear any parameters that you explicitly want to set to NULL. -- Tim Young Elevate Software www.elevatesoft.com |
« Previous Page | Page 2 of 2 | |
Jump to Page: 1 2 |
This web page was last updated on Saturday, April 27, 2024 at 08:52 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |