Re: Why "Name IsNull is not declared"?

Tech-Archive recommends: Fix windows errors by optimizing your registry

In that case, you'd be best off asking in a newsgroup related to VB.Net,
such as microsoft.public.dotnet.languages.vb

This newsgroup is for questions about Access, the database product that's
part of Office Professional (which uses VBA)

--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)


"Jeffery B Paarsa" <JeffBPaarsa@xxxxxxxxx> wrote in message
news:F5827B8E-2425-4D17-8533-B6D971C2B6C4@xxxxxxxxxxxxxxxx
Hello,

thanks, but I am not using VBA I am using VB studio 2005. I am getting
this
error inside ot VB editor. I closed the project and opened it but it did
not
helped.
--
Jeff B Paarsa


"John W. Vinson" wrote:

On Mon, 1 Jun 2009 20:51:01 -0700, Jeffery B Paarsa
<JeffBPaarsa@xxxxxxxxx>
wrote:

I am getting a curly blue line under IsNull "Name IsNull is not
declared"?
Why is that? What am I missing?

This appears to be the very common References bug. Open any
module in design view, or open the VBA editor by typing
Ctrl-G. Select Tools... References from the menu. One of the
..DLL files required by Access will probably be marked
MISSING. Uncheck it, recheck it, close and open Access.

If none are MISSING, check any reference; close and open
Access; then uncheck it again. This will force Access to
relink the libraries.
--

John W. Vinson [MVP]



.

Quantcast