VBA, CDO vs Outlook 2000 Object Library?? (Outlook Newbie)

CDO vs Outlook 2000 Object Library?? (Outlook Newbie)

Author	Message
James Brimicomb #1 / 6	CDO vs Outlook 2000 Object Library?? (Outlook Newbie) Hi Just got Outlook 2000. This is probably a stupid question but.. a) If using Outlook 2000, what's the advantage of using the (optionally installable) CDO library over using the Outlook 9.0 Object Library? b) If I already have Outlook (2000) running, can I use GETOBJECT from Access to define a reference to the visible application or not? I have tried Set objOL = GetObject ("Outlook.Application") to no avail, whilst Set ObjOL = New Outlook.Application works fine... And.. c) If you're logging onto an Exchange Server when launching Outlook, can that be automated too from code?? Is this where CDO comes in?? Any answers or part answers to any of the above welcome!! Ta v much James Brimicombe Cambs County Council
Sat, 15 Feb 2003 03:00:00 GMT

Neo #2 / 6	CDO vs Outlook 2000 Object Library?? (Outlook Newbie) Answers will be inline to your comments/questions. Quote: > Hi > Just got Outlook 2000. This is probably a stupid question but.. > a) If using Outlook 2000, what's the advantage of using the (optionally > installable) CDO library over using the Outlook 9.0 Object Library? Some messaging objects/properties are not exposed by the Outlook object library and CDO comes in very handy to balance out the missing features. (Note: Outlook object model much easier to work with, but doesn't support code running under a service. CDO is supported from a service. Also Outlook does not expose the Address Book list you see when pressing CTRL + SHIFT + B while CDO does.) Quote: > b) If I already have Outlook (2000) running, can I use GETOBJECT from Access > to define a reference to the visible application or not? I have tried > Set objOL = GetObject ("Outlook.Application") to no avail, whilst > Set ObjOL = New Outlook.Application works fine... Yes. Try: GetObject (,"Outlook.Application") 'Note the comma Quote: > And.. > c) If you're logging onto an Exchange Server when launching Outlook, can > that be automated too from code?? Is this where CDO comes in?? You could try the following using the Outlook Object model, but I don't know if it will work because I usually kick things off with CDO. Set objOutlook = CreateObject("Outlook.Application") Set objNameSpace = objOutlook.GetNamespace("MAPI") ' Set the False to True to get the Profile picker objNamespace.logon "profilename", "password", False, True Cheers... /Neo
Sat, 15 Feb 2003 03:00:00 GMT

Sue Mosher [MVP #3 / 6	CDO vs Outlook 2000 Object Library?? (Outlook Newbie) a) CDO has a few UI elements that Outlook doesn't -- such as popping up the Address Book -- and can be faster on routines that iterate over items in a folder. b) Try using CreateObject instead. c) Outlook already has a Namespace.Logon method that lets you specify a profile and password. What CDO gives you is the ability to run multiple sessions, which can be handy for going through other mailboxes. -- Sue Mosher Author of "Teach Yourself Microsoft Outlook 2000 Programming in 24 Hours" "Microsoft Outlook 2000 E-mail and Fax Guide" Outlook and Exchange solutions at http://www.slipstick.com Quote: > Hi > Just got Outlook 2000. This is probably a stupid question but.. > a) If using Outlook 2000, what's the advantage of using the (optionally > installable) CDO library over using the Outlook 9.0 Object Library? > b) If I already have Outlook (2000) running, can I use GETOBJECT from Access > to define a reference to the visible application or not? I have tried > Set objOL = GetObject ("Outlook.Application") to no avail, whilst > Set ObjOL = New Outlook.Application works fine... > And.. > c) If you're logging onto an Exchange Server when launching Outlook, can > that be automated too from code?? Is this where CDO comes in?? > Any answers or part answers to any of the above welcome!! > Ta v much > James Brimicombe > Cambs County Council
Sat, 15 Feb 2003 03:00:00 GMT

James Brimicomb #4 / 6	CDO vs Outlook 2000 Object Library?? (Outlook Newbie) Ta Sue! If I use CDO, then I can access the Address Book and validate parameterised Mail Names? Or do rather I bought your book than replying to this? ;-) Quote: > a) CDO has a few UI elements that Outlook doesn't -- such as popping up the > Address Book -- and can be faster on routines that iterate over items in a > folder. > b) Try using CreateObject instead. > c) Outlook already has a Namespace.Logon method that lets you specify a > profile and password. What CDO gives you is the ability to run multiple > sessions, which can be handy for going through other mailboxes. > -- > Sue Mosher > Author of > "Teach Yourself Microsoft Outlook 2000 Programming in 24 Hours" > "Microsoft Outlook 2000 E-mail and Fax Guide" > Outlook and Exchange solutions at http://www.slipstick.com > > Hi > > Just got Outlook 2000. This is probably a stupid question but.. > > a) If using Outlook 2000, what's the advantage of using the (optionally > > installable) CDO library over using the Outlook 9.0 Object Library? > > b) If I already have Outlook (2000) running, can I use GETOBJECT from > Access > > to define a reference to the visible application or not? I have tried > > Set objOL = GetObject ("Outlook.Application") to no avail, whilst > > Set ObjOL = New Outlook.Application works fine... > > And.. > > c) If you're logging onto an Exchange Server when launching Outlook, can > > that be automated too from code?? Is this where CDO comes in?? > > Any answers or part answers to any of the above welcome!! > > Ta v much > > James Brimicombe > > Cambs County Council
Mon, 17 Feb 2003 03:00:00 GMT

James Brimicomb #5 / 6	CDO vs Outlook 2000 Object Library?? (Outlook Newbie) Thanks v much for your detailed replies - the problem I may have is distributing an Access Applicationt that can tap into the client's Outlook & send messages/orders etc - If I don't know their PROFILE name (and password), I'm stuffed - but then, if I put 'TRUE' into the SHOW DIALOG parameter they will log in for me if they've not loaded Outlook already... I'll try that! Ta again Quote: > Answers will be inline to your comments/questions. > > Hi > > Just got Outlook 2000. This is probably a stupid question but.. > > a) If using Outlook 2000, what's the advantage of using the (optionally > > installable) CDO library over using the Outlook 9.0 Object Library? > Some messaging objects/properties are not exposed by the Outlook object > library and CDO comes in very handy to balance out the missing features. > (Note: Outlook object model much easier to work with, but doesn't support > code running under a service. CDO is supported from a service. Also > Outlook does not expose the Address Book list you see when pressing CTRL + > SHIFT + B while CDO does.) > > b) If I already have Outlook (2000) running, can I use GETOBJECT from > Access > > to define a reference to the visible application or not? I have tried > > Set objOL = GetObject ("Outlook.Application") to no avail, whilst > > Set ObjOL = New Outlook.Application works fine... > Yes. Try: > GetObject (,"Outlook.Application") 'Note the comma > > And.. > > c) If you're logging onto an Exchange Server when launching Outlook, can > > that be automated too from code?? Is this where CDO comes in?? > You could try the following using the Outlook Object model, but I don't know > if it will work because I usually kick things off with CDO. > Set objOutlook = CreateObject("Outlook.Application") > Set objNameSpace = objOutlook.GetNamespace("MAPI") > ' Set the False to True to get the Profile picker > objNamespace.logon "profilename", "password", False, True > Cheers... > /Neo
Mon, 17 Feb 2003 03:00:00 GMT

Sue Mosher [MVP #6 / 6	CDO vs Outlook 2000 Object Library?? (Outlook Newbie) Neither CDO nor Outlook supports resolution of parameterized addresses -- all addresses need to be string literals, but either model gives you access to the Address Book and name resolution capability. -- Sue Mosher Author of "Teach Yourself Microsoft Outlook 2000 Programming in 24 Hours" "Microsoft Outlook 2000 E-mail and Fax Guide" Outlook and Exchange solutions at http://www.slipstick.com Quote: > Ta Sue! > If I use CDO, then I can access the Address Book and validate parameterised > Mail Names? Or do rather I bought > your book than replying to this? ;-) > > a) CDO has a few UI elements that Outlook doesn't -- such as popping up > the > > Address Book -- and can be faster on routines that iterate over items in a > > folder. > > b) Try using CreateObject instead. > > c) Outlook already has a Namespace.Logon method that lets you specify a > > profile and password. What CDO gives you is the ability to run multiple > > sessions, which can be handy for going through other mailboxes. > > > Hi > > > Just got Outlook 2000. This is probably a stupid question but.. > > > a) If using Outlook 2000, what's the advantage of using the (optionally > > > installable) CDO library over using the Outlook 9.0 Object Library? > > > b) If I already have Outlook (2000) running, can I use GETOBJECT from > > Access > > > to define a reference to the visible application or not? I have tried > > > Set objOL = GetObject ("Outlook.Application") to no avail, whilst > > > Set ObjOL = New Outlook.Application works fine... > > > And.. > > > c) If you're logging onto an Exchange Server when launching Outlook, can > > > that be automated too from code?? Is this where CDO comes in?? > > > Any answers or part answers to any of the above welcome!! > > > Ta v much > > > James Brimicombe > > > Cambs County Council
Tue, 18 Feb 2003 19:35:41 GMT

Page 1 of 1

[ 6 post ]