application defined error / invalid use of null

[markjkubicki]

new error: (and not certain when it started ... which would have been insightful)

on a FormOpen event:
application defined error... invalid use of NULL()

tried stepping through the code as it opens ... to no avail

about how to trap this error:
any suggestions / directions on where to look / maybe a good previous post or article?

...came across a random article suggesting that i de-compile (?) (and then proceed to describe what seemed to be an obtuse method required to do so?) ...and then re-compile
any thought on this ? (the project has been worked on fairly heavily over several years and has never been "de-compiled")

as always, with much appreciation in ADVANCE,


mark

[pbaldy]

What is the code? The problem may be data related, a field being Null that never was before.

Decompiling is a valuable tool in the toolbox. I haven't used it in quite a while but it's certainly something I'd try with an error that I couldn't track down.

[Welshgasman]

So you are saying, you cannot put a breakpoint on the very first line in that form?
Even to add a MSGBOX so you have something to start with?

To decompile, all you need is to add the /decompile switch when opening access? I just have a shortcut set up to do mine.

"C:\Program Files\Microsoft Office\Office12\MSACCESS.EXE" /decompile

http://www.fmsinc.com/microsoftacces.../decompile.asp

[markjkubicki]

never-mind.... found it ...thank you

lesson learned:
sometimes it is better to check when you see a blatantly misspelled word (name of a control) in a subroutine, than to presumed you had just dragged your elbows across the keyboard and caused it to be misspelled.

(Q. why does a lesson learned ALWAYS take so much time ? =:-)

yet again, thnx
m.

[Welshgasman]

Do you have Option Explicit at the top of every module?

[markjkubicki]

...i "try" to be diligent (and mostly am)