VBA standard functions unknown ???

I made a macro for a customer, but when he runs it he gets "compilation
error" at standard functions like Left or Str ...
How is it possible ??? I sent him a .swp macro with references to VBA and
SolidWorks 2003 type library...
This is the first time in years it happens... COuld it be a problem when
installing SW on his side ?

 

I have had problems spuratically with these functions. I remedied it by
calling them directly.
VBA.Left()
instead of
Left()

Regards,

Corey Scheich

 

I've had string functions fail, and in most cases it traced back to other
objects that were not being properly implemented. For some reason, other
seemingly unrelated issues throw off the string funcs. Can't explain it,
but I've seen it. Does your customer have a SW2004 type library instead of
SW2003? The real glitch may actually be with the SW objects, even though
it's not complaining at that point and may even seem to work. You could try
making sure the type libraries are consistent, and then the string funcs may
straighten themselves out. They (the string funcs) seem to be an indicator
that something is slightly amiss, even if it's something that VB has already
figured out how to work around.

For what it's worth,
Brenda

 

Perhaps, just perhaps, the full boat of VBA has not been loaded. I know
when I was developing some custom VBA and functions in excel, I need to
reload (additional add-in's) for VBA and full excel functionality. Maybe
the two (SW and Office) use common VBA functionality and it has not been
fully implemented on your customer's machines. Just a thought.

Keith

 

it may be different if he is running office 97 insted of office 2000.
if this is true them ask him to install the latest service pack for
97. after that id say get office 2000.

 

Anti Virus software is often known to prevent VBA from installing properly.