MicrosoftWord 2000

I've been having a problem with my Word program. When I open a new page, I end up with 5 pages rather than one. Also, whenever I close Word, I get the message: Microsoft Visual Basic Run-time error '13': Type mismatch
I tried the Help -- Detect and Repair option, but nothing changed. What can be done to repair this?

 

It might be an error in you default template (normal.dot). If you delete or rename that file, Word will create a new clean one on next start of Word. I'd start by trying that. Default location for Normal.dot is within your profile:

{path to your profile}\Application Data\Microsoft\Templates

You need to have rights to view hidden files to see the Application Data folder.

 

Thanks for the suggestion. That did get rid of the extra four pages, but didn't do anything to get rid of the run-time error when I exit Word. Any idea what that is or how to address it?

 

Hi, Barry.

Perhaps Event Viewer will provide additional helpful details about the error. I suspect your errors will be described in the "Application" section or "System" section.

Instructions About How to Access and Use "Event Viewer ":

• Click Start.
• Right-click My Computer.
• Select "Manage" to open the "Computer Management" window.
  (Event Viewer will be displayed under the "System Tools" directory item.)
• Expand "Event Viewer" and then select "Application ", "Security ", and "System" to view the logs.
• Look for "error" events that occurred around the time your problem occurred. These events will be displayed as icons with either a white X on red background or a black exclamation point on yellow background. In the security section of Event Viewer, events of possible concern are ones that display a padlock icon instead of a key icon.
• Double-click on an individual event to open the "Event Properties" window which shows details about the event.
  • You can use the up/down arrow buttons in the "Event Properties" window to move your focus to other events in the list.
  • Use the button below the up/down arrows to copy the details for an event to your clipboard for pasting elsewhere.
  • Click on the "http://go.microsoft.com/fwlink/events.asp" link in the "Event Properties" window to view more information from Microsoft about the event.

 

No events were recorded at the time that the error message came up. Thanks for the suggestion though.

 

I think there are three likely places for closing errors:

Add-ins. Do you have any add-ins installed. I'd start by disabling these and see if that cures the problem. You access the add-ins from the tools menu: Tools > Templates and Add-ins

Default printer Word ties into the default printer (to set up page sizes for example). You can get problems in printer drivers affecting Word. So try selecting a different default printer (if you have a choice), remove any rogue printers (failed install, or old printers you no longer use), and uninstall special printers like PDF printers (if you have the source to reinstall them).

Word itself It could be that Word itself has become corrupted. You can uninstall and reinstall Word without reinstalling all of office. To reinstall word (you will need the office source disk to complete this!):

1. Go to Add/Remove programs in control panel. Select Office and click on the Change button
2. In the Office setup GUI, select Add or Remove Features
3. In the next screen click on the selector to the left of "Microsoft Word for Windows" and change it to "Not Available "
4. Click on the Update now button.

That will uninstall Word. Reboot the PC and then repeat the procedure above. However this time change the selector at step 3 to "Run from My Computer ". That will reinstall Word

 

Thanks for the suggestions. I've addressed these issues and nothing changes. I think I'll just accept the slight annoyance of having to click off the error window every time I close Word. It isn't causing any problem, other than that.

 

Have a look at this article I found with a google search:

http://www.tech-archive.net/Archive/Word/microsoft.public.word.application.errors/2004-04/0914.html

 

Reggie, that appears to be the answer. I'll be tied up for a few days, but I'll get back here with the results when I am able to do this fix. Thanks for sharing.