Component not correctly registered (Word 2000 (9.0))

[GeekConsultant]

I created an application for a client who needed to convert thousands of WordPerfect documents to Word (9.0 or 2000). I discovered that the majority of these documents were quite similar and a simple generic template with some VBA to get some information from the user was all that was required to have the client move forward. During the user testing phase, one user who runs on a Win98 desktop got a very simple error message in a standard vbError msgbox - Titled "Microsoft Visual Basic" and "Component not correctly registered" containing OK and Help buttons. There is no indication WHAT is not correctly registered (terrible usability engineering) and pressing Help generates no topic. This error occurs upon opening the document in runtime or opening the DOT file and trying to get into the VB editor. User must cick OK at least 20 times (each time the msgbox re-appears) before one of two things occur - her computer freezes and after 10 minutes shuts itself down hard (requiring scandisk) or Word shuts down. I was able to "unprotect" and get into the VB Editor on the user's system by alternating ESC and OK. Looking in the References did not indicate any "missing" component. The only thing used that's not enabled by default for my code is MSScripting (used to check for existence of folders and files) - I tried removing and re-enabling this item and the Forms object library to no avail. My development environment was Win2KPro. Could the differences between the FM20 and SCRRUN DLLs being in different directories on Win2K (WINNTSystem32) be the key here? Please, does anyone have
experience or a step-by-step troubleshooter for this? I hate running blind using trial-and-error brute techniques in the user's presence...

Thanks

The Geek
-> one who keeps an eye on the foundation of the
fragile pedestal currently standing upon...

[pieterse]

My very first suspicion would be a defective install. Have you tried Help, detect and repair (or the one from the Setup program)?

Another test could be to prepare a disk with exported code + forms and try to import them on the offending system (into a new document). If that fails, I would distrust that system.

Another thing to consider is a cleanup job for the code.

[GeekConsultant]

<img src=/S/blackteeth.gif border=0 alt=blackteeth width=20 height=20> I thought about a defective install - this environment is network installed from images - getting install CD would require an act of God... - and the user would lose some files local to her machine (She wasn't exactly happy to learn that I may need to re-image. Apparently, she'd saved significant info locally even though company policy frowns on local usage). I was looking to other possiblilities, first, just to be nice and give the user time enough to clean up her own mess <img src=/S/sigh.gif border=0 alt=sigh width=15 height=15>

Exporting code(s)&form(s) to a disk and sneaker net <img src=/S/salute.gif border=0 alt=salute width=15 height=20>... I'll try that

Clean up MY code??? But...but...it's not dirty... <img src=/S/exclamation.gif border=0 alt=exclamation width=15 height=15>

The Geek

[doj]

Couple of things to check
Is there a referenced template, if so the problem could exist there
Does your project or referenced project access environment variables, are these available to win98
is the path to the users share hardcoded or derived.
If the user logs on to a 2k machine does the same error occur
What happens if you put a breakpoint into the startup template and step it.
Sorry these are not the answer but may point you in the correct direction.

[GeekConsultant]

Well... It was a simple thing... Rather than re-installing Office 2000 blindly, I followed the following steps:

1) Exported the code for "ThisDocument" to a share in some temporary folder
2) Exported the forms (there were two) to that share
3) Did some more research on 336 Error (which I discovered related to this "Component not properly registered" error message) on MSDN and Knowledgebase
4) Found one note somewhere that mentioned something about the VB6 runtime DLL (VBRUN60):
http://download.microsoft.com/download/vb6...-US/VBRun60.exe
Application KB Article: http://support.microsoft.com/default.aspx?...kb;en-us;192461
5) Found one note somewhere that mentioned something about the register service: http://download.microsoft.com/download/acc...US/Regsv32a.exe
Application KB Article: http://support.microsoft.com/default.aspx?...kb;en-us;182500
Applicable KB Article: http://support.microsoft.com/default.aspx?...kb;en-us;161983
6) Did some more research... <img src=/S/yawn.gif border=0 alt=yawn width=15 height=15>
7) Went to the user's system.
a) Opened a new blank document.
[img]/forums/images/smilies/cool.gif[/img] Popped open the VBEditor
c) Opened Tools-References
d) Selected Microsoft Forms 2.0 Object Library and Microsoft Scripting Runtime
e) Opened View-Object Browser and ran through a few Forms and Scripting Objects
f) OK - so those are there - pressed HELP (F1) on a couple of object properties - they DID NOT COME UP!!!! No Error Message.
g) hmmmm....
8) Tried -> installing vbrun60.exe
9) Ran through all the items in #7 again - all seems good.
10) Loaded the problem child application that bombed before - IT RUNS!

PROBLEM SOLVED! <img src=/S/bananas.gif border=0 alt=bananas width=33 height=35>

Solution: Installed VBRUN60.EXE (See KB 192461)

The Geek