You receive a "ActiveX component can't create object" error message when using Access
This article was previously published under Q319844
For a Microsoft Access 2000 version of this article, see 319841 (http://support.microsoft.com/kb/319841/ ) .
Novice: Requires knowledge of the user interface on single-user computers.
For a Microsoft Access 97 version of this article, see 296205 (http://support.microsoft.com/kb/296205/ ) .
On This Page
SYMPTOMS
When you use Microsoft Access, you receive the following error message: ActiveX...
When you use Microsoft Access, you receive the following error message:
This article describes some common causes for this error message and offers methods that you can use to resolve the issue.
ActiveX component can't create object
CAUSE
This behavior can occur if any of the following conditions are true: Data Access...
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.
RESOLUTION
Cause 1: DAO is not properly registered Resolution On the computer that hosts Mi...
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.6 library, use the following command: regsvr32 "C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL"
Cause 2: One or more references are missing
Resolution
- Open the database for which you receive the error message.
- Press ALT+F11 to open the Microsoft Visual Basic Editor.
- In the Visual Basic Editor, click References on the Tools menu.
- 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.
- Press ALT+F11 to open the Visual Basic Editor.
- In the Visual Basic Editor, click References on the Tools menu.
- 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. Collapse this table
Operating system Location Windows XP \Windows\System32 Windows NT and Windows 2000 \Winnt\System32 Windows 95, Windows 98, and Windows Millennium Edition \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 the following Sysinternals Web site: Sysinternals (http://technet.microsoft.com/en-us/sysinternals/default.aspx)
Cause 5: There is a damaged wizard file
Resolution
- Use Windows Explorer to locate the following wizard files: Acwzmain.mde, Acwztool.mde and Acwzlib.mde.
- Change the file name extension of each file to "old." For example, change Acwzmain.mde to Acwzmain.old.
- Reinstall Access to restore the files.
MORE INFORMATION
The third-party products that this article discusses are manufactured by compani...
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
No comments:
Post a Comment