Not IsNull error

G

G

I used an access template to build a database and it contains "Not isnull" in
the coding. It worked fine on my computer, but as soon as I loaded it on the
client's computer, it errored out.
What would cause this not to work?
 
M

Marshall Barton

G said:
I used an access template to build a database and it contains "Not isnull" in
the coding. It worked fine on my computer, but as soon as I loaded it on the
client's computer, it errored out.
Click to expand...


I don't see how it ever worked. There is no such thing as
Not IsNull. In a VBA procedure you can use something like:
Not IsNull(variableorfieldname)
or in a query you can use:
Not fieldname Is Null or fieldname Is Not Null

If that's what you are really doing then, check the
references, they may be different or missing on the other
computer. If this is the source of the problem, this might
be useful: http://allenbrowne.com/ser-38.html
 
G

G

Marshall,
Thank you for your quick response.
I used a sample database in ACCESS, like the "inventory database"
And yes, it is VBA code
And yes, it does contain "Not IsNull(variableorfieldname)
"
I had just shortened it for this email.
The thing is that the program is not recognizing that function. The
fieldname does not matter. It just won't recognize the function.

I already checked the references and used only the same ones that were in
the sample database.

Any other suggestions?
 
M

Marshall Barton

G said:
I used a sample database in ACCESS, like the "inventory database"
And yes, it is VBA code
And yes, it does contain "Not IsNull(variableorfieldname)
"
I had just shortened it for this email.
The thing is that the program is not recognizing that function. The
fieldname does not matter. It just won't recognize the function.

I already checked the references and used only the same ones that were in
the sample database.
Click to expand...


No guarantee that a sample db has it's references set the
same way you need them on your system. Some samples add a
reference that they don't even need.

When a builtin VBA function is not recognized, it is almost
always some(?) other reference that's the wrong version, an
uninstalled library, or even the right version that is
installed in a different place. Go back to Allen's article
and read it carefully.

In the future, please use Copy/Paste for any code that you
need help with. It's a waste of everyone's time to try to
debug some paraphrased code.
 
Top