Microsoft Knowledge Base Article
This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved.
Terms
of Use |
Trademarks
Article ID: 296205 - Last Review: March 27, 2007 - Revision: 3.3
ACC: Error Message: ActiveX Component Can't Create Object
This article was previously published under Q296205
For a Microsoft Access 2000 version of this article, see
319841Â
(http://kbalertz.com/Feedback.aspx?kbNumber=319841/EN-US/
)
.
Novice: Requires knowledge of the user interface on single-user computers.
On This Page
SYMPTOMS
When you use Microsoft Access, you receive the following error message:
ActiveX component can't create object
This article describes some common causes for this error message and offers methods that you can use to resolve the issue.
CAUSE
This behavior can occur if any of the following conditions are true:
- Data Access Objects (DAO) is not properly registered.
-or- - One or more references are missing.
-or- - There is a utility database reference that is not valid.
-or- - You do not have the required permissions for required libraries.
-or- - There is a damaged wizard file.
-or- - The Office compatibility script is not run after you install access on the terminal server.
RESOLUTION
Cause 1: DAO Is Not Properly Registered
Resolution
- On the computer that hosts Microsoft Windows Terminal Server or the computer on which Microsoft Access is installed, click Start, and then click Run.
- Type regsvr32 followed by the path to your DAO file. Enclose this path in quotation marks. For example, to register the DAO 3.5 library, use the following command:
regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO350.DLL"
Cause 2: One or More References Are Missing
Resolution
- Open the database for which you receive the error message.
- Click the Modules tab, and then click New.
- On the Tools menu, click References.
- Examine the list of libraries. If any items are marked as "MISSING," locate the library file and re-associate the reference. Or, click to clear the check box next to the library name.
Cause 3: There Is a Utility Database Reference That Is Not Valid
Resolution
- Open the database for which you receive the error message.
- Click the Modules tab, and then click New.
- On the Tools menu, click References.
- Click to clear the check box next to any reference to Utility Database or Utility.mda.
Cause 4: You Do Not Have the Required Permissions for Required Libraries
Resolution
- Make sure that users have "read" permissions for all files in the following folders:
Operating System Location
--------------------------------------
Windows NT, 2000, XP \Winnt\System32
Windows 95, 98, Me \Windows\System
- If you cannot grant read permissions, you can use a utility such as FileMon to determine which file or files the users do not have the required permissions to use.
To obtain FileMon, visit to the following Sysinternals Web site:
Sysinternals
(http://www.microsoft.com/technet/sysinternals/default.mspx)
Cause 5: There Is a Damaged Wizard File
Resolution
- Use Windows Explorer to locate the following wizard files: Wzmain80.mde, Wztool80.mde and Wzlib80.mde.
- Change the file name extension of each file to "old." For example, change Wzmain80.mde to Wzmain80.old.
- Reinstall Access to restore these files.
Cause 6: Office Compatibility Script Is Not Run After You Install Access on the Terminal Server
Resolution
Locate the office compatibility script in the Scripts folder, and then run it.
MORE INFORMATION
The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
APPLIES TO
- Microsoft Access 97 Standard Edition
Retired KB Content DisclaimerThis article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
Community Feedback System
Very often, it takes hours to solve a problem. Very often, you've looked high
and low, and have tried a lot of solutions. When you finally found it, chances
are, it was because someone else helped you. Here's your chance to give back.
Use our community feedback tool to let others know what worked for you and what
didn't.
Please also understand that the community feedback system is not warranted to be
correct, it's simply a system that we've built to let people try and help each
other. If something in a feedback response doesn't make sense to you, or you're
not comfortable making changes that the feedback talks about (like registry
edits), please consult a professional.
Thank you for using kbAlertz.com Feedback System.
-- Scott Cate
Be the first to leave feedback, to help others about this knowledge base
article.
(Optional) Name
(Optional)
Public URL Or Email
Comments
No
HTML -- Text Only Please