Thanks, Bill.

I've also done some searching - same experience. Thanks for the
disabling tip - didn't work in this instance.

My understanding is growing and I'm beginnning to suspect that it is not
a pure Excel problem.

The destination environment is Win2K/Excel2K and it is there that I've
had the problems.

The workbook works fine on:
XP2K3/Excel2k3
XP2K2/Excel2K2 and
XP2K2/Excel2K
- so I assumed that it was the client's Excel2K installation (blind to
the operating system differences).

(Win98/Excel97 exhibits the same problem, but doesn't really concern me,
as the client doesn't run them.)

Last night I installed the same Excel2K as is on the XP2K2 machine, onto
the Win2K machine and got the same results, so it can't be the Excel
install that is the problem (used same install CD set - no upgrades or
patches in either case).

So my options a

1. It's an operating system issue. (I.e. the XP install carries the
library).

2. The reason it works on the XP/Excel2K machine is because of other
software already installed on it - it's a development machine - like
some VB libraries.

I'll keep searching, but would be grateful for any further thoughts you
have. It seems strange to me that VB should spit the dummy on a TRIM
statement!

(We can happily write our own TRIM function, but are concerned that
there is more to it than that).

Thanks a lot for replying.

Rgds

GB

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!