I am using isnull() in a SQL expression for building a recordset.
The problem is, on PCs the application is deployed to, error 3085
occurs: "Undefined function 'IsNull' in expression."

The code works great both in the development environment and in the
EXE on development PCs, but not on PCs the application is installed
on. I assume there is a missing or outdated library on the client
PCs where this is occuring. However, normal troubleshooting hasn't
uncovered what it might be. I've compared file listings from the
bad PCs with the good ones, temporarily removed all files from
the good PCs which were not on the bad PCs, and the good PCs still
work fine. Perhaps a library on both systems is not being properly
registered on some? The application in question has quite a bit
of other SQL code which has, to date, worked successfully. I find
it interesting that the first occurance of a simple function like
IsNull in a query would cause a problem like this.

Any ideas? For reference, the knowledge base has nothing related.
The environment is VB4 - 16 bit running under any OS.

Tony Hamilton

You know what I would suggest is you can not always believe in the error
msg from the system. Could be something very irrelevant. I have some
very bad experience in believing in the system error msg's but things
turned out to be something else.

In this respect, VB 4.0 can not be trusted so much as VB 3.0.
Jeff HONG YAN