The missing calendar reference caused the left() to stop working. And the
left() wasn't associated with the calendar.

Aren't you kind of nervous that there will be a next line that will blow up
because of that still missing reference?

(I'd fix the reference.)



KaiRich wrote:

Using VBA.Left() or Strings.Left() does work. I had to do
it for all string functions (left, right, trim, etc.). I
am making the change to the model and re-issuing to the
users. Thanks, Kai.
-----Original Message-----
Hi,
I have seen that on xl97 but not after that version. You
should get this error from any function from the Strings
module from VBA. Check in the Object browser for Strings,
you'll get all the functions: UCase, Left, Right,
Format, ...
To prevent this from happening, you uncheck/recheck
the 'Missing' library. However, it has to be done on each
machine.
Another way (the one i use) is to use the code
syntax 'module.function' to help VBA figure it out. eg:
Strings.UCase(s)
Strings.Left(s,2)
...
It has to be done for any occurence in the code, but once
done, you shouldn't have to go on every machine.
--
Regards,
Sébastien


"KaiRich" wrote:

Hi all,
I have a few PCs that are crashing on the vb
function 'Left'(). When any macro uses the 'Left'
function
the PC crashes with "Compile Error: Can't find object
or
library'.
I have searched the MS knowledge base, but the only
articles suggest opening the references box and
unchecking
the offending library, but the routines for finding
which
is the offending library don't work in this situation
(nor
do I think that it is a valid solution to this
problem).
What dll, ocx, olb, etc. is missing or corrupted to
cause
vb to crash on such a basic function? Or is something
else
causing this and if so how do I resolve it?
Thanks in advance, Kai

.


--

Dave Peterson