In excel VBA, this is a consistent indicator of exaclty what you said - a
Missing reference not related to VBA. Why it always seems to flag a VBA
built in function I can't say - perhaps it is the first time it consults the
references - but invarialble the answer that corrects this problem is to fix
the MISSING reference.
--
Regards,
Tom Ogilvy
"Rick Rothstein (MVP - VB)" wrote:
> >>In the VBA editor, click on Tools/References and see if anything
> >>is marked as "Missing". If so, check the item or items and then
> >>try your code again.
> > ...
> >>"Ed" <jag_manR__EM*-0_V_E...@sbcglobal.net> wrote in message
> >>> . . . e.g., Mid(), Trim(), UCase(). . . .
> >
> > Mid, Trim and UCase are built into VBA itself. OP would have had to
> > have removed references to VBA itself, but that'd mean more than just
> > the string functions would have failed.
>
> Well, the OP did say "e.g. (for example)"<g>, so he may only be reporting
> String function because they are what he saw first. As for the OP removing
> the reference... I don't think he can... however, for reasons I have never
> been able to find out (over in the compiled VB side of thing, at least), the
> system can decide, on its own, to remove one or more references. When it
> does, the kind of problems the OP is reporting usually is the result. The
> only other way I've seen these commands cease working is when a variable in
> the same scope as the attempted function call is named the same as the
> built-in function (for example, naming a module level variable mID... short
> for module ID). However, this seems unlikely here because of the number of
> functions involved.
>
> Rick
>
>
|