Update on Access 97 and = NULL

Hiroshi asked me to reproduce the problem WRT Access 97 and NULLs. I
could not. A couple of years ago the problem was appearing on the
interfaces list as some users using ODBC were experiencing the problem.
After about 1/2 day trying to reproduce it under a new operating system,
upgrades of MDAC etc. I finally gave up. However, I did find this
explanation as to why on the Microsoft Knowledge Base:

http://support.microsoft.com/support/kb/articles/Q237/9/92.ASP

I'm not quite sure of the sequence of events and conditions at this
point. But it appears that if someone uses the Form's filter function,
it makes a call into the Jet, which generates what it thinks is an ODBC
compatible query, submits the query to the ODBC driver, which forwards
it on to the database. Depending upon your version of MDAC and the Jet
engine, the Forms filter function will *not* exhibit the behavior. If it
can be pinned down, then we (we meaning you guys ;-)) can rip out the "
= NULL " hack and simply tell users that encounter the problem to
upgrade their MDAC components. If someone knows under what condition
Access 97 would be running under Jet 3.5 vs. Jet 4.0, and whether an
upgrade of the downloadable MDAC components includes Jet upgrades, it
would help.

Mike Mascari
mascarm(at)mascari(dot)com