Skip to main content
A
Anonymous
December 5, 2007
Answered

MS VB Run-Time Error '13': Type Mismatch

  • December 5, 2007
  • 1 reply
  • 2546 views
Hi,
I'm new to the forum, and just starting a trial of RH7 as my company decides whether we'll upgrade from our X4 product or switch to a different HAT. Before attempting to import my existing HPJ project, I opened the sample Application Help project. Frequently when I switch among topics, I get a Microsoft Visual Basic dialog box that says Run-Time Error '13': Type Mismatch. I have to click the End button to close the dialog box. Does anyone have any idea what causes the error? I got that error also in X4 when switching among topics in my own project (on a different computer).
This topic has been closed for replies.
Correct answer
Hello Brian,
I'm thrilled!!! Your clue was enough to set me in the right direction, so after spending many hours searching for the solution to this problem lately and in the past, it appears to finally be solved. Initially just unchecking the other add-ins didn't do the trick, and the situation seemed to get worse and worse--I couldn't save files because Word kept giving me error messages that macros were disabled (which I didn't know how to rectify), and RH kept freezing. I noticed after a while that the RoboHelp menu in Word would have disappeared when RH froze, and that the template would have changed to Normal.dot. If I reattached the RoboHelp.dot template, RH would unfreeze, but later the template would switch back to Normal and RH would freeze again. I was initimidated to edit the registry. Finally I came upon this page http://personal-computer-tutor.com/NNTWord.htm where the author Linda gave the path to the Word startup folder where I found some templates whose filenames were preceded by tildes (corrupt?). I deleted those and other junk and I temporarily deleted the normal.dot template at Linda's suggestion. Since then, the run-time errors have no longer occurred and the other problems have not recurred. I THINK I'm back on track! I'm thrilled because my boss encouraged me to uninstall and re-install Office and migrate to different HAT, a time-consuming process I'd rather avoid at least until the current release is completed. Thank you so much for your help!!

1 reply

A
Anonymous
December 10, 2007
Hello ADguru,

Welcome to the forums.

Most runtime error are caused by an Add-In trying to run and failing. This is a word related problem.In Tools\Templates and Addins, check to see if there are any there. If so uncheck and see if that helps. If not, I would suggest checking the Microsoft sites for instruction to check the registry for any wayward addin references.

Post back and let us know how you get on.

Hope this helps,

Brian
A
Anonymous
Correct answer
December 13, 2007
Hello Brian,
I'm thrilled!!! Your clue was enough to set me in the right direction, so after spending many hours searching for the solution to this problem lately and in the past, it appears to finally be solved. Initially just unchecking the other add-ins didn't do the trick, and the situation seemed to get worse and worse--I couldn't save files because Word kept giving me error messages that macros were disabled (which I didn't know how to rectify), and RH kept freezing. I noticed after a while that the RoboHelp menu in Word would have disappeared when RH froze, and that the template would have changed to Normal.dot. If I reattached the RoboHelp.dot template, RH would unfreeze, but later the template would switch back to Normal and RH would freeze again. I was initimidated to edit the registry. Finally I came upon this page http://personal-computer-tutor.com/NNTWord.htm where the author Linda gave the path to the Word startup folder where I found some templates whose filenames were preceded by tildes (corrupt?). I deleted those and other junk and I temporarily deleted the normal.dot template at Linda's suggestion. Since then, the run-time errors have no longer occurred and the other problems have not recurred. I THINK I'm back on track! I'm thrilled because my boss encouraged me to uninstall and re-install Office and migrate to different HAT, a time-consuming process I'd rather avoid at least until the current release is completed. Thank you so much for your help!!
A
Anonymous
December 17, 2007
Hello ADguru,

Glad I was able to put you on the right track. Most VB runtime errors point more to Word, than RH. A useful place for word application problems is Microsoft Communities Forums. Might see you there sometime

Thanks for the update. It is usefull for others who may experience the same problem.

Brian
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices