Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Word 2000--run-time error 13, type mismatch.

Status
Not open for further replies.

jfhewitt

Technical User
Jun 6, 2000
287
US
Get the error message when closing Word. I think I may have narrowed the problem to 2 programs that may have loaded macros when installed...IBM Via Voice amd the Windows XP fax program. At first it caused Word to "not respond", but after some modifications of the Via Voice parameters it now only gives the error message, then ends normally. Any ideas? I surmise that some programs load their own macros, why may contain data mismatch problems...ergo the error.
 
This error disappeared when I uninstalled Via Voice. I am sure it was caused by a macro loaded during installation. I reinstalled and the error 13 came back. Is there any way to track down macros that are loaded by sharing programs? Where are they? Can they be deleted?
 
In word go to "tools" then "macro" and then click "macros"

Its probably best if you do this before you install via voice to see what macros are installed, then do it again afterwards and make a comparison.

Once you have found the new "corrupt" macro simply delete it from within this macro dialog box.


 
Make sure you check through all the possibilities in the dropdown "Macros in".

Even better, select Tools > Customize. Select Macros. Scroll through the list on the right. It will list the macros...but also indicates where they are from. For example, if there is a global template loaded, its name will show here.

Gerry
 
Thanks...I think I have found the offending macro, but I can't delete it...the delete button is greyed out. What now?
 
If you went through David's step, the file that contains the macro will be selected in the "Macros in" drop down . If you went my route, the name of file (actually the VB project) will be listed. eg."Project.NewMacros.macroname.

In either case, you need to find out what file is loading the macro.

If it is Normal.dot, make a copy of it (just in case), and then delete it. If you have your own macros stored there...well, that is why you should not store your macros in normal.dot, unless you absolutely have to. Sometimes you have to delete normal.dot.

Also, check under Tools > Templates and Addins. If it is loaded as a global it should be listed there. Try unchecking it.

Also check under Tools > COM Addin. If it is a voice software, I suspect it may be there. I would think plug-in type software would use COM.

But you have to know what the is file that is loading the macro first. Then try not loading it. The fact that is greyed out makes me think it is likely a COM.

Gerry
 
I think I've located the macro files, and debugged them...all OK. Can't open file containing "voicedoc" macros, don't have the password. Is there a default password?
 
Default password? No I would not think so. What would be the point of a default password? Sounds like you had better contact the software supplier. If they have a macro in a password protected file, they (hopefully) should be able to help. Eityher ask them for access (the password) so you can try and debug it, or maybe get a replacement.

Are you saying you can not prevent it from loading? What happens when you stop it from loading?


Gerry
 
Some programs have strings like "password" as a default. Since Via Voice is an IBM program, good luck on getting any help. In any event, I've got it where the only inconvenience is the Visual Basic "error 13" window, and then Word closes without incident. I better leave well enough alone...I've never seen a more difficult program to install and reinstall than Via Voice...Big Blue getting even with the little guys. Thanks for all your efforts.
 
I am not knowledgable in this area, but I'm posting the following in case it is applicable...


Towards the bottom of the article, it states:

ADO vs. DAO
If you include references to both ADO and DAO in the same project, you may have some difficulty. Both use a Recordset object, so the following code is ambiguous:
Code:
Dim r as recordset
You may receive the following error message:
runtime error 13: datatype mismatch

To specify which object model you want to use, include a qualifier in front:
Code:
Dim s As ADODB.Recordset
Dim t As DAO.Recordset
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top