>According to this page:
>
>http://support.microsoft.com/kb/295619/en-us
>
>Microsoft says the IsNull(fax.value) will evaluate to False when fax.value =
>Null.
... using Access 2002. Not other versions.
>Well it's a good thing I didn't bother to read that article until afer
>I started using IsNull.
[quoted text clipped - 5 lines]
>article. Now I am not sure why what they say doesn't work. Is this true for
>Nz in a DAP? Is it always true? I don't get it. Maybe someone does?
This was a bug in one version. It's been fixed.
>I am accepting to try the Nz workaround since what I been using "doesn't
>work."
This was a bug in one version. It's been fixed.
>And yes this does work. But I would like to try the workarounds using Nz as
>Microsoft says to achieve the above.
Reread the article, in particular the "Applies To".
John W. Vinson [MVP]
You've got the choice of using an obscure non-supported bug or using
supported clear code and you want to use the bug?
Go with the code, it's easier to read and in a years time when you have to
revisit it you won't be wondering how these controls are getting hidden.
If you have to upgrade from the bugged version you wont have to revisit the
form to do this properly.
Just use code.

Signature
--
Terry Kreft
> According to this page:
>
[quoted text clipped - 45 lines]
> George Hester
> _________________________________