Accessing CDO 1.21 failure

  • Thread starter Thread starter Anthony Yio
  • Start date Start date
A

Anthony Yio

Hello,

I have Office 2003 professional installed. So, I guess the CDO 1.21 is
bundled with. When I try to use Ole/Com Object viewer to view the Typelib
content of Microsoft CDO 1.21 library.
(TypeLibID{3FA7DEA7-6438-101B-ACC1-00AA00423326})

It give me error saying

"LoadRegTypeLib({3FA7DEA7-6438-101B-ACC1-00AA00423326}, 1, 33, 1033, ...)
failed
Library not registered
TYPE_E_LIBNOTREGISTERED($8002801D)


I am positively sure that the CDO.dll was there and check that the in
the Add/Remove component of the office that the CDO object libraries was
selected. I even try to use Regsvr32 the CDO.dll to resolve this problem but
it seems no luck. I have found another CDO that ship with my XP pro.

uuid(CD000000-8B95-11D1-82DB-00C04FB1625D),
version(1.0),
helpstring("Microsoft CDO for Windows 2000 Library"),


It is working though but I need to use CDO 1.21 instead of the CDO for
windows.

Any reason why this was failed?
 
CDO Sys in not the same as CDO 1.21. I suspect that CDO 1.21 is not
installed or what is installed is a CDO from an earlier version of Outlook,
which won't work with Outlook 2003. If you open your Outlook VBA project
(Alt+F11) and select Tools, References and you can't see CDO.DLL (CDO 1.21)
then it's not installed.

Select Change in Add/Remove Programs after selecting Office and then follow
the wizard steps to modify your installation. Expand the Outlook tree and
see if Collaboration Data Objects (CDO) is set to run from your hard drive.
Have your Office CD handy.
 
which won't work with Outlook 2003. If you open your Outlook VBA project
(Alt+F11) and select Tools, References and you can't see CDO.DLL (CDO 1.21)
then it's not installed.
Click to expand...

Yup, I can see the CDO 1.21 in the references, but, I can't see the exposed
function in the OleView cause it prompt error message as mentioned when I
try to view the class. Any COM objects should be viewable in OLEView (OLE
Object viewer) View program cause the program only lay out the exposed
interfaces and functions. If it is not viewable in OLEView, it is by theory
and should be not usable?

I have reinstalled the Office 2003 and yet no luck. I have even manually
deleted
the CDO.dll and have the installer to re-register itself (CDO 1.21) but
still no luck.

Previously, I was using Office XP small office edition and later upgraded to
Office 2003 pro. I was wondering if it was the previous installation
corrupted the registry entry or block it from having CDO 1.21 accessible?

Also, on the other hand, is the CDO 1.21 accessible on Office 2003?

Or, the CDO 1.21 is not accessible by OleView program. Can anyone view the
CDO 1.21 interfaces of Office 2003 in the OleView?



Regards,
Anthony.
 
I have tested to use the Object Browser in VB.NET to view the content of the
CDO 1.21.
Well,It seems displaying the info of the exposed functions. Actually, I am
not using VB to develop my app but I guess I have to live with it to check
out the functions and interfaces exposed.
 
I have no idea what OLEView is. If you can see the CDO 1.21 methods and
properties in the Object Browser in the Outlook VBA project then CDO is
registered correctly. You certainly can access CDO 1.21 from Outlook 2003 if
it's installed, I do it all the time.

Upgrades can be a problem sometimes, usually though it's the profile that
has problems. I have seen cases where an upgrade left the earlier version of
CDO installed and didn't install the appropriate one for Outlook 2003
however. In cases like that it was fixed either by running Detect and Repair
for Outlook from the Help menu or by uninstalling Office and then
reinstalling without the earlier version of Outlook present.
 
Back
Top