Hi,

We were using Outlook 2003 and everything was working fine. Now we hava
planned to shift to Outlook 2007. But we found the "Microsoft CDO 1.21
Library" missing in Office 2007." while running VBA script which was working
fine in Outlook 2003. Could any one please let me know what is the similar
file or simple solution is there to overcome this error. Will it require to
change our complete/all scripts which uses this library?

Thanks,
Paresh

CDO 1.21 is not included with Outlook 2007 but can be downloaded from
http://www.microsoft.com/downloads/d...displaylang=en.

However, because CDO 1.21 is not supported in managed code, it's pretty
irrelevant to VSTO add-ins, which are the topic of this forum. You should
post any future Outlook VBA questions "down the hall" at
http://www.microsoft.com/office/comm....program_v ba.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"masani paresh" wrote:

We were using Outlook 2003 and everything was working fine. Now we hava
planned to shift to Outlook 2007. But we found the "Microsoft CDO 1.21
Library" missing in Office 2007." while running VBA script which was working
fine in Outlook 2003. Could any one please let me know what is the similar
file or simple solution is there to overcome this error. Will it require to
change our complete/all scripts which uses this library?

Thanks Sue for reply.

That means if we migrate to use outlook 2007 then it will need to distribute
CDO1.21 to all 1000s machines after dowloading from the link given by you?
If yes then don't we have any other alternative?

Thanks,
Paresh

"Sue Mosher [MVP-Outlook]" wrote:

CDO 1.21 is not included with Outlook 2007 but can be downloaded from
http://www.microsoft.com/downloads/d...displaylang=en.

However, because CDO 1.21 is not supported in managed code, it's pretty
irrelevant to VSTO add-ins, which are the topic of this forum. You should
post any future Outlook VBA questions "down the hall" at
http://www.microsoft.com/office/comm....program_v ba.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"masani paresh" wrote:

We were using Outlook 2003 and everything was working fine. Now we hava
planned to shift to Outlook 2007. But we found the "Microsoft CDO 1.21
Library" missing in Office 2007." while running VBA script which was working
fine in Outlook 2003. Could any one please let me know what is the similar
file or simple solution is there to overcome this error. Will it require to
change our complete/all scripts which uses this library?

The alternatve would be to rewrite your code to use Outlook 2007 native
objects such as PropertyAccessor and StorageItem to accomplish whatever
you're doing with CDO 1.21.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx



"masani paresh" wrote:

That means if we migrate to use outlook 2007 then it will need to distribute
CDO1.21 to all 1000s machines after dowloading from the link given by you?
If yes then don't we have any other alternative?

"Sue Mosher [MVP-Outlook]" wrote:

CDO 1.21 is not included with Outlook 2007 but can be downloaded from
http://www.microsoft.com/downloads/d...displaylang=en.

However, because CDO 1.21 is not supported in managed code, it's pretty
irrelevant to VSTO add-ins, which are the topic of this forum. You should
post any future Outlook VBA questions "down the hall" at
http://www.microsoft.com/office/comm....program_v ba.

"masani paresh" wrote:

We were using Outlook 2003 and everything was working fine. Now we hava
planned to shift to Outlook 2007. But we found the "Microsoft CDO 1.21
Library" missing in Office 2007." while running VBA script which was working
fine in Outlook 2003. Could any one please let me know what is the similar
file or simple solution is there to overcome this error. Will it require to
change our complete/all scripts which uses this library?

Moreover, The http://msdn.microsoft.com/en-us/library/bb226711.aspx says that
CDO has been consolidated into the Outlook 2007 object. Is this means that
CDO's functions will be available under the Outlook Object Model. If I
enabled Outlook 12.0 Object then will it work?

Thanks,
Paresh

"Sue Mosher [MVP-Outlook]" wrote:

The alternatve would be to rewrite your code to use Outlook 2007 native
objects such as PropertyAccessor and StorageItem to accomplish whatever
you're doing with CDO 1.21.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx



"masani paresh" wrote:

That means if we migrate to use outlook 2007 then it will need to distribute
CDO1.21 to all 1000s machines after dowloading from the link given by you?
If yes then don't we have any other alternative?

"Sue Mosher [MVP-Outlook]" wrote:

CDO 1.21 is not included with Outlook 2007 but can be downloaded from
http://www.microsoft.com/downloads/d...displaylang=en.

However, because CDO 1.21 is not supported in managed code, it's pretty
irrelevant to VSTO add-ins, which are the topic of this forum. You should
post any future Outlook VBA questions "down the hall" at
http://www.microsoft.com/office/comm....program_v ba.

"masani paresh" wrote:

We were using Outlook 2003 and everything was working fine. Now we hava
planned to shift to Outlook 2007. But we found the "Microsoft CDO 1.21
Library" missing in Office 2007." while running VBA script which was working
fine in Outlook 2003. Could any one please let me know what is the similar
file or simple solution is there to overcome this error. Will it require to
change our complete/all scripts which uses this library?

That depends on what you're trying to do with CDO. As I indicated in my
earlier post, Outlook 2007 has many new objects that provide almost (but not
quite) complete parity with CDO operations. You must, of course, rewrite your
code to use those new objects.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"masani paresh" wrote:

Moreover, The http://msdn.microsoft.com/en-us/library/bb226711.aspx says that
CDO has been consolidated into the Outlook 2007 object. Is this means that
CDO's functions will be available under the Outlook Object Model. If I
enabled Outlook 12.0 Object then will it work?

"Sue Mosher [MVP-Outlook]" wrote:

The alternatve would be to rewrite your code to use Outlook 2007 native
objects such as PropertyAccessor and StorageItem to accomplish whatever
you're doing with CDO 1.21.

"masani paresh" wrote:

That means if we migrate to use outlook 2007 then it will need to distribute
CDO1.21 to all 1000s machines after dowloading from the link given by you?
If yes then don't we have any other alternative?

"Sue Mosher [MVP-Outlook]" wrote:

CDO 1.21 is not included with Outlook 2007 but can be downloaded from
http://www.microsoft.com/downloads/d...displaylang=en.

However, because CDO 1.21 is not supported in managed code, it's pretty
irrelevant to VSTO add-ins, which are the topic of this forum. You should
post any future Outlook VBA questions "down the hall" at
http://www.microsoft.com/office/comm....program_v ba.

"masani paresh" wrote:

We were using Outlook 2003 and everything was working fine. Now we hava
planned to shift to Outlook 2007. But we found the "Microsoft CDO 1.21
Library" missing in Office 2007." while running VBA script which was working
fine in Outlook 2003. Could any one please let me know what is the similar
file or simple solution is there to overcome this error. Will it require to
change our complete/all scripts which uses this library?

Thanks Sue for your help.

I think the better solution is to distribute the CDO 1.21 because rewrting
the code will involve lots of works.

but I could not understand why outlook versions are not compatible. I have
worked on so many MS technology and I found is compatible with one another.
and I think MS has been known for its maintaining the compatibility feature
with the s/f versions.

Thanks,
Paresh

"Sue Mosher [MVP-Outlook]" wrote:

That depends on what you're trying to do with CDO. As I indicated in my
earlier post, Outlook 2007 has many new objects that provide almost (but not
quite) complete parity with CDO operations. You must, of course, rewrite your
code to use those new objects.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"masani paresh" wrote:

Moreover, The http://msdn.microsoft.com/en-us/library/bb226711.aspx says that
CDO has been consolidated into the Outlook 2007 object. Is this means that
CDO's functions will be available under the Outlook Object Model. If I
enabled Outlook 12.0 Object then will it work?

"Sue Mosher [MVP-Outlook]" wrote:

The alternatve would be to rewrite your code to use Outlook 2007 native
objects such as PropertyAccessor and StorageItem to accomplish whatever
you're doing with CDO 1.21.

"masani paresh" wrote:

That means if we migrate to use outlook 2007 then it will need to distribute
CDO1.21 to all 1000s machines after dowloading from the link given by you?
If yes then don't we have any other alternative?

"Sue Mosher [MVP-Outlook]" wrote:

CDO 1.21 is not included with Outlook 2007 but can be downloaded from
http://www.microsoft.com/downloads/d...displaylang=en.

However, because CDO 1.21 is not supported in managed code, it's pretty
irrelevant to VSTO add-ins, which are the topic of this forum. You should
post any future Outlook VBA questions "down the hall" at
http://www.microsoft.com/office/comm....program_v ba.

"masani paresh" wrote:

We were using Outlook 2003 and everything was working fine. Now we hava
planned to shift to Outlook 2007. But we found the "Microsoft CDO 1.21
Library" missing in Office 2007." while running VBA script which was working
fine in Outlook 2003. Could any one please let me know what is the similar
file or simple solution is there to overcome this error. Will it require to
change our complete/all scripts which uses this library?

Regarding compatibility, Outlook object model code *is* compatible between
versions, as long as you use only objects, properties, methods, and events
from the oldest version of Outlook you want to support. You certainly can't
expect new features introduced in the latest version to be back-ported to
older versions.

The CDO 1.21 object model is an entirely different matter. It's a dead end
technology with no new features added in years and probably no one remaining
at Microsoft who completely understands it. Now that the bulk of its
functionality is available in native Outlook objects, Microsoft has no reason
to include it with Outlook and every reason to try to deter people from using
it so they can get rid of it completely at some point.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx



"masani paresh" wrote:

Thanks Sue for your help.

I think the better solution is to distribute the CDO 1.21 because rewrting
the code will involve lots of works.

but I could not understand why outlook versions are not compatible. I have
worked on so many MS technology and I found is compatible with one another.
and I think MS has been known for its maintaining the compatibility feature
with the s/f versions.

Thanks,
Paresh

"Sue Mosher [MVP-Outlook]" wrote:

That depends on what you're trying to do with CDO. As I indicated in my
earlier post, Outlook 2007 has many new objects that provide almost (but not
quite) complete parity with CDO operations. You must, of course, rewrite your
code to use those new objects.

"masani paresh" wrote:

Moreover, The http://msdn.microsoft.com/en-us/library/bb226711.aspx says that
CDO has been consolidated into the Outlook 2007 object. Is this means that
CDO's functions will be available under the Outlook Object Model. If I
enabled Outlook 12.0 Object then will it work?

"Sue Mosher [MVP-Outlook]" wrote:

The alternatve would be to rewrite your code to use Outlook 2007 native
objects such as PropertyAccessor and StorageItem to accomplish whatever
you're doing with CDO 1.21.

"masani paresh" wrote:

That means if we migrate to use outlook 2007 then it will need to distribute
CDO1.21 to all 1000s machines after dowloading from the link given by you?
If yes then don't we have any other alternative?

"Sue Mosher [MVP-Outlook]" wrote:

CDO 1.21 is not included with Outlook 2007 but can be downloaded from
http://www.microsoft.com/downloads/d...displaylang=en.

However, because CDO 1.21 is not supported in managed code, it's pretty
irrelevant to VSTO add-ins, which are the topic of this forum. You should
post any future Outlook VBA questions "down the hall" at
http://www.microsoft.com/office/comm....program_v ba.

"masani paresh" wrote:

We were using Outlook 2003 and everything was working fine. Now we hava
planned to shift to Outlook 2007. But we found the "Microsoft CDO 1.21
Library" missing in Office 2007." while running VBA script which was working
fine in Outlook 2003. Could any one please let me know what is the similar
file or simple solution is there to overcome this error. Will it require to
change our complete/all scripts which uses this library?

Just to add to what Sue mentioned, you are not allowed to deploy CDO
yourself, you have to download it from the Web distribution on the MS Web
site. You can of course write code to do that. I'd definitely agree with Sue
about CDO being dead end technology.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Sue Mosher [MVP-Outlook]" wrote in message
...
Regarding compatibility, Outlook object model code *is* compatible between
versions, as long as you use only objects, properties, methods, and events
from the oldest version of Outlook you want to support. You certainly
can't
expect new features introduced in the latest version to be back-ported to
older versions.

The CDO 1.21 object model is an entirely different matter. It's a dead end
technology with no new features added in years and probably no one
remaining
at Microsoft who completely understands it. Now that the bulk of its
functionality is available in native Outlook objects, Microsoft has no
reason
to include it with Outlook and every reason to try to deter people from
using
it so they can get rid of it completely at some point.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

Thanks a lot Sue and Ken for your detailed information.

Thanks,
Paresh

"Ken Slovak - [MVP - Outlook]" wrote:

Just to add to what Sue mentioned, you are not allowed to deploy CDO
yourself, you have to download it from the Web distribution on the MS Web
site. You can of course write code to do that. I'd definitely agree with Sue
about CDO being dead end technology.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"Sue Mosher [MVP-Outlook]" wrote in message
...
Regarding compatibility, Outlook object model code *is* compatible between
versions, as long as you use only objects, properties, methods, and events
from the oldest version of Outlook you want to support. You certainly
can't
expect new features introduced in the latest version to be back-ported to
older versions.

The CDO 1.21 object model is an entirely different matter. It's a dead end
technology with no new features added in years and probably no one
remaining
at Microsoft who completely understands it. Now that the bulk of its
functionality is available in native Outlook objects, Microsoft has no
reason
to include it with Outlook and every reason to try to deter people from
using
it so they can get rid of it completely at some point.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx