When I was working normally in Word 2000 under Windows 98SE, the program closed for some not-obvious reason. When I opened it again, all toolbars were missing, and I had the following error message: Microsoft Visual Basic Run-time error '2147024809 (80070057)': Can't move focus to the control because it's invisible, not enabled or of a type that does not accept the focus. (End of error message) I can use Word as long as I remember keyboard shortcuts. There is nothing I can do to get the menus back. I have used the Office 2000 setup program to repair my installation and to uninstall and reinstall. Still with no success. I have reverted to the registry of this morning, before the problem occurred. Also no help. I also renamed Normal.dot, so that Word created a new file by that name; to no avail. I have searched the Microsoft KB with no help. I did find reference to several error messages with this error code, but they referred to different problems and not mine. I've come to the conclusion that the problem is not in Office, but somewhere in my Windows installation. Briefly (Office 2000 is installed on C:), I formatted D:, installed Windows and then Office, after having told the BIOS that only D: is present. (C: and D: are separate physical drives.) Then I operated Word successfully on D:. Next, I rebooted and made both disks operative. I booted into C:, and then used the Word that I had just installed on D:. And the result was the same as for the Word installed on C:. Then I rebooted, using only the second disk, and Word was normal. Thus, it is clear that the problem is not in the Office installation. Am I right? Is there a solution? NEW DEVELOPMENT: There has been no improvement, and the error message has not changed, but the error number has! The new error message number is: Run-time error '-2147352565 (8002000b)' What can I do, short of formatting and starting all over, which is an unacceptable solution for me?

Hi Ira This looks like the problem you are having, but the solution isn't what you want to hear, I'm afraid: Read this This discussion looks quite old, so you may want to see if Microsoft ever did build a solution before taking the someone drastic rebuild step. I looked for a virus but couldn't find an exact match - but I didn't look very hard. I would suggest this course of action first. Hope this is of help to you Tom