When comparing variant values using:

varNew <> varOld  

I get an invalid procedure call 5.  

In this case the values are the same,  4 charater string containing
Chr(0), Chr(0), Chr(0), Chr(63) or Null, Null, Null, ?

In windows 2K, this does not fail.
In windows 98 It does.

I am not sure as to why, but I believe that because of the first charater being a
NULL, the <> is treating them both as NULL.  This may be the problem.

Any comments or ideas about this problem and why it works in 2K but not 98 would
be appreciate.  

A character can't be Null, so something else
is going on.  What do you get if you type this
in in the immediate window:

print VarType(varNew), VarType(varOld)

When comparing variant values using:

varNew <> varOld

I get an invalid procedure call 5.

In this case the values are the same,  4 charater string
containing
Chr(0), Chr(0), Chr(0), Chr(63) or Null, Null, Null, ?

In windows 2K, this does not fail.
In windows 98 It does.

I am not sure as to why, but I believe that because of the first
charater being a
NULL, the <> is treating them both as NULL.  This may be the
problem.

Any comments or ideas about this problem and why it works in 2K
but not 98 would
be appreciate.

For one of the (at least five different) meanings of "Null" it certainly
can: it can equal VBNullChar = Chr$(0)

I suspect the original poster has sussed the source of his problem.  Wish I
knew how to help him with it...

Jim Deutch
MS Dev MVP