Runtime error

[TM]

Hi,

For the last two years i've had "run time error 429" come up every time I
open
a document - I know it's got something to do with VB but try as I have I've
not
got rid of this nuisance, I've tried ms procedures, other stuff, nothing
works, is
there any tool available to get rid of this thing ?

Thanks,

TM

 

[TF]

This is usually a third party add-in, but read my colleague Beth's expert
adivse below!

--
Office MVP Beth Melton advises:

A "runtime" error means that there is an error in a macro or add-in that is
attempting to run. Typically these macros are created by a third-party and
are not part of the Word installation. (They could also be caused by a
malfunctioning macro virus as well)

Many third-party applications will create an add-in and place it in the
Office\Startup folder or use a COM add-in (DLL) to integrate their software
with Word. Another common add-in, the "Microsoft Works Suite Add-in for
Word" can only be found in your Add/Remove programs list.

Aside from the Works Suite Add-in, to determine if you have any add-ins you
can check for them using the following:

Go to Tools/Templates and Add-Ins and see if there are any global templates
or add-ins listed. If you find any then chances are they are located in
your Office\Startup folder or Word\Startup folder.

The location of the Word\Startup folder can be found under
Tools/Options/File Locations and the Office\Startup fold




:
: Hi,
:
: For the last two years i've had "run time error 429" come up every time I
: open
: a document - I know it's got something to do with VB but try as I have
I've
: not
: got rid of this nuisance, I've tried ms procedures, other stuff, nothing
: works, is
: there any tool available to get rid of this thing ?
:
: Thanks,
:
: TM
:
:

 

[TM]

tried all this and no good ...
ActiveX component can't create object or return reference to this object
(Error 429)


Creating objects requires that the object's class be registered in the
system registry and that any associated dynamic-link libraries (DLL) be
available. This error has the following causes and solutions:

a.. The class isn't registered. For example, the system registry has no
mention of the class, or the class is mentioned, but specifies either a file
of the wrong type or a file that can't be found.
If possible, try to start the object's application. If the registry
information is out of date or wrong, the application should check the
registry and correct the information. If starting the application doesn't
fix the problem, rerun the application's setup program.

b.. A DLL required by the object can't be used, either because it can't be
found, or it was found but was corrupted.
Make sure all associated DLLs are available. For example, the Data Access
Object (DAO) requires supporting DLLs that vary among platforms. You may
have to rerun the setup program for such an object if that is what is
causing this error.

c.. The object is available on the machine, but it is a licensed
Automation object, and can't verify the availability of the license
necessary to instantiate it.
Some objects can be instantiated only after the component finds a license
key, which verifies that the object is registered for instantiation on the
current machine. When a reference is made to an object through a properly
installed type library or object library, the correct key is supplied
automatically.

If the attempt to instantiate is the result of a CreateObject or GetObject
call, the object must find the key. In this case, it may search the system
registry or look for a special file that it creates when it is installed,
for example, one with the extension .lic. If the key can't be found, the
object can't be instantiated. If an end user has improperly set up the
object's application, inadvertently deleted a necessary file, or changed the
system registry, the object may not be able to find its key. If the key
can't be found, the object can't be instantiated. In this case, the
instantiation may work on the developer's system, but not on the user's
system. It may be necessary for the user to reinstall the licensed object.

d.. You are trying to use the GetObject function to retrieve a reference
to class created with Visual Basic.
GetObject can't be used to obtain a reference to a class created with
Visual Basic.

e.. Access to the object has explicitly been denied.
For example, you may be trying to access a data object that's currently
being used and is locked to prevent deadlock situations. If that's the case,
you may be able to access the object at another time.

For additional information, select the item in question and press F1 (in
Windows) or HELP (on the Macintosh).

----- Original Message -----
From: "TF" <terryfarrell%40%6d%73%6e%2ecom>
Newsgroups: microsoft.public.word.application.errors
Sent: Wednesday, August 23, 2006 9:51 PM
Subject: Re: Runtime error