From MSDN Net (for us Microsoft Certified Developers), here is what it
has to say about Error 429. Of course, this generally applies to older
version of the Office Suite as well. Try implementing your dialog boxes
per their recommendation and it should go away. It is a Runtime vs.
Developer implementation of the Common Dialog Control and it would make
sense that an older Windows/Office as well as the Mac/Office combos
would be the ones having problems as most everyone else probably got
either SBE or Office Pro (or Office 2K) with their systems which allow
for development using the controls, not just a runtime version of the
controls. It probably goes away if you've downloaded some other
application that was written in VB and uses the Common Dialog Control.
In general, if the user has Access, they should have the developer
version of it, which both Pro (obviosly) and SBE (Small Business
Edition) of Office generally come with. Only the Home edition of Office
doesn't include Access, but that is why it runs from $49 to $99, instead
of the $199 or higher for the other editions.
-Rob Bolin
Sr. Java and VisualStudio Developer
STAR BASE Consulting, Inc.
------------------------------- MSDN Info Follows
···
----------------------------------
OFF2000: Error Message: Run-time Error 429: ActiveX Component Can't
Create Object (Q281848)
------------------------------------------------------------------------
--------
The information in this article applies to:
Microsoft Excel 2000
Microsoft Access 2000
Microsoft Word 2000
Microsoft Outlook 2000
Microsoft PowerPoint 2000
Microsoft Project 2000
Microsoft Visio 2000 Standard Edition
Microsoft Visual Basic for Applications
------------------------------------------------------------------------
--------
SYMPTOMS
When running code that calls the Common Dialog Control (Comdlg32.ocx) on
a computer other than the one on which the code was developed, you may
receive the following error message:
Run-time error 429: ActiveX component can't create object.
CAUSE
This problem can occur if the following conditions are true:
The control is called from Visual Basic for Applications code by using
the New CommonDialog command.
The computer on which you are running the code has a run-time license
rather than a design-time license for this control.
With a run-time license, you can load the control but you cannot create
or insert it. The design-time license for this control ships with the
Microsoft Office 2000 Developer Edition or Microsoft Visual Studio. It
does not ship with other versions of Microsoft Office 2000.
WORKAROUND
To work around this problem, wrap the control inside another control,
such as a UserForm. To do this, follow these steps:
In the Visual Basic Editor, add a UserForm to your project.
Insert a common dialog control on the UserForm. For example, use the
following code to call the common dialog control on the UserForm:
Sub test()
UserForm1.CommonDialog1.ShowOpen
End Sub
Save the workbook.
Becuase the control is wrapped in the UserForm and resides inside the
project, you can now call it in run-time mode.
------------------------------------------------------------------------
--------
Published Jul 3 2001 6:05AM Issue Type kbprb
Last Modifed Jul 12 2001 4:55PM Additional Query Words XL2000 OFF2000
WD2000 OL2000 PPT2000
Keywords kberrmsg kbdta kbdtacode KbVBA