I am getting the “type mismatch on external name” error on a class that is in a script library. The script library is one of many in a template that many databases inherit from. When I make a change to any routine in the library I follow these steps: 1) recompile all LotusScript 2) sign temp, both all design and all data documents, from admin 3) copy template to servers for over night auto-design refresh.
The problem is, is that those agents which call the class get the type mismatch error even though no code in the class changed, requiring me to recompile all script in the production database. Earlier posts refer to the same problem (http://www-10.lotus.com/ldd/nd6forum.nsf/55c38d716d632d9b8525689b005ba1c0/6ec8bdc42bb554d085256e51001d2a45?OpenDocument) but I guess I am still doing something wrong.
Are we not able to put classes into re-usable and shareable libraries?
Thanks for the help.
Ron
Subject: type mismatch on external name error
I am interested in reponses to this question. Pre-6 I had to jump through hoops to resolve this type of problem. For my applications, the Recompile All Lotusscript has since worked…but apparently there are instances where it does not work as desired.
Subject: type mismatch on external name error
Run the code throug the debugger and see what line it is complaining about. Chances are you are doing something like
dim doc as notesdocument, item as notesitem
set d = someview.getfirstdocument
set item = doc.getfirstitem(“Someitem”)
print item.vlaues(0)
Or something of a like nature. Basically something that would compile ok but fail at runtime.
Subject: RE: type mismatch on external name error
I don’t get the error with the debugger on - which leads me to believe it has to do with recompile of the script.
Thanks for your help.
Ron
Subject: Same problem here
It seems to be just with classes in script libraries. Whenever we make a change to a class in a script library in the template, it works fine, then we refresh it out and production databases start delinking themselves and this error message starts coming up. Recompile all LotusScript helps, or just save the class definition and then the code where it’s used (without making any changes, add a space remove a space) and you’re good to go again. Very annoying.
Subject: RE: Same problem here
I’ve got the same problem as well. Has anyone heard of a fix, or why this is happening?