Office 2003, ArcMap: could it be a problem

I'm experiencing a strange thing, a package of programs written and working on more than 20 computers is not working on our new pc that has, different from the other machines, Office 2003 and ArcMap installed on it. The strange thing is that, while debugging the problem, it comes out that the instruction that stuck's is a simple:

Left$(myString, Len (myString)-nChars)

Any suggestions.
Thanks René

 

René, Try it as such...

Left$(myString, (Len(myString) - nChars))

 

That's typically a missing reference.

 

Sorry, I've transcribed wrong the example.
What I don't understand is that these progs work well with no errors on all the other machines of the office, but these have Office XP installed on them and non ArcMap.
The problem is not in the program or on the references, what I suspect, but I'm not sure is that Office 2003 or ArcMap, install or substitute some kind of library/dll that is different than the usual VBE6.DLL.

 

I don't have ArcMap but run the same function
on apps using Office03..gl...

 

Here's the ArcMap referance:
Function Left$(String As String, Length As Long) As String
Which is using the VBA.string referance. My referances in ArcMAP is pointing
to this file
C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL (Date
of Jan 12, 2001)
The same as my AutoCAD2005 (Map2005) and Office 2000

Murph

all the other machines of the office, but these have Office XP installed on
them and non ArcMap.

but I'm not sure is that Office 2003 or ArcMap, install or substitute some
kind of library/dll that is different than the usual VBE6.DLL.

 

Rene,

I've run into the same thing periodically, It comes down to having two
..DLL's with either Left$ or Len defined as slightly different functions. To
correct it, I had to use the full definition of the function. That is making
the call as VBA.Left$(myString, VBA.Len (myString)-nChars)

Try looking at the Object Browser in the VBA IDE and doing a search for both
Left$ and Len on the problem machine...I suspect you'll find a .DLL loaded
that you didn't expect with the same function name....

Regards,

Tom

working on more than 20 computers is not working on our new pc that has,
different from the other machines, Office 2003 and ArcMap installed on it.
The strange thing is that, while debugging the problem, it comes out that
the instruction that stuck's is a simple:

 

Thanks Tom, That was thew problem!!!