By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
435,264 Members | 1,056 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 435,264 IT Pros & Developers. It's quick & easy.

Invalid use of null -- After testing for null

P: 80
I'm pulling data from a field on a form, evaluating whether or not it's null, then calculating based on the data in the field. Here's my code for evaluating the field:

intAdvanced = IIf(Not IsNull(Me.txtAdvanced), CLng(Me.txtAdvanced), 0)

So if the field's not null, it Converts it to a Long and sets the variable to that, otherwise, the variable is 0.

However, the program's erroring on this line, Run-Time 94, invalid use of Null! How can I be using null invalid, when, in fact, I'm specifically changing the value to 0 if it's null?
May 19 '08 #1
Share this Question
Share on Google+
3 Replies

P: 80
BTW - Immediate Window

x = Isnull(Me.txtAdvanced)
? x

So Access knows the value is null.
May 19 '08 #2

Expert 100+
P: 378
intAdvanced = IIf(IsNull(Me.txtAdvanced), 0, CLng(Me.txtAdvanced))


intAdvanced = Nz(Me.txtAdvanced, 0)
May 19 '08 #3

Expert Mod 15k+
P: 31,494
An unfortunate side-effect of using IIf() within VBA code (not the same within SQL strangely enough) is that VBA evaluates all parameters before passing them to the function.

I guess you can see now why you got that error in your code :)

Nz() is clearly the better way to code this so you should be fine if you follow MegaLog's suggestion.
May 21 '08 #4

Post your reply

Sign in to post your reply or Sign up for a free account.