Home |
Search |
Today's Posts |
#1
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I have Excel files that are used by people with different
version of MS Office. These files create an Outlook object and send emails. The issue is, when a person with Outlook 2002 uses the file, Excel is smart enough to switch to the Microsoft Office 10.0 Object Library. However, next next person with Outlook 2000 receives compile errors when the Excel code runs. When I look at the references, it shows, MISSING Microsoft Office 10.0 Object Library. I have to uncheck that and recheck Microsoft Office 9.0 Object Library. Is there anyway to handle this with code? TIA Nelson |
#2
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Nelson,
use late binding. Here's a link to an Outlook example of converting from early to late binding that I gave earlier this year http://tinyurl.com/yhls -- HTH Bob Phillips ... looking out across Poole Harbour to the Purbecks (remove nothere from the email address if mailing direct) "Nelson" wrote in message ... I have Excel files that are used by people with different version of MS Office. These files create an Outlook object and send emails. The issue is, when a person with Outlook 2002 uses the file, Excel is smart enough to switch to the Microsoft Office 10.0 Object Library. However, next next person with Outlook 2000 receives compile errors when the Excel code runs. When I look at the references, it shows, MISSING Microsoft Office 10.0 Object Library. I have to uncheck that and recheck Microsoft Office 9.0 Object Library. Is there anyway to handle this with code? TIA Nelson |
#3
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Hi Nelson
... Excel is smart enough to switch to the Microsoft Office 10.0 Object Library. .... and after all this she's stupid enough to actually save the upgrade for all later users, yes that goes for ADO and other references too. Bob's right as far as I know, you can't handle this without removing the references and create late binding by code. This posting just to add another resource, Dick Kusleika's page http://www.dicks-clicks.com/excel/olAutomating.htm -- HTH. Best wishes Harald Followup to newsgroup only please. "Nelson" wrote in message ... I have Excel files that are used by people with different version of MS Office. These files create an Outlook object and send emails. The issue is, when a person with Outlook 2002 uses the file, Excel is smart enough to switch to the Microsoft Office 10.0 Object Library. However, next next person with Outlook 2000 receives compile errors when the Excel code runs. When I look at the references, it shows, MISSING Microsoft Office 10.0 Object Library. I have to uncheck that and recheck Microsoft Office 9.0 Object Library. Is there anyway to handle this with code? TIA Nelson |
#4
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
I copied the code from the url you provided. Having
problems: If remove the Outlook reference, I get a compile error User Defined Type not Defined on Set objOutlook = New Outlook.Application If I keep the Outlook reference I get a syntax error on Set objRecipient.add("Hicks, Nelson") -----Original Message----- Nelson, use late binding. Here's a link to an Outlook example of converting from early to late binding that I gave earlier this year http://tinyurl.com/yhls -- HTH Bob Phillips ... looking out across Poole Harbour to the Purbecks (remove nothere from the email address if mailing direct) "Nelson" wrote in message ... I have Excel files that are used by people with different version of MS Office. These files create an Outlook object and send emails. The issue is, when a person with Outlook 2002 uses the file, Excel is smart enough to switch to the Microsoft Office 10.0 Object Library. However, next next person with Outlook 2000 receives compile errors when the Excel code runs. When I look at the references, it shows, MISSING Microsoft Office 10.0 Object Library. I have to uncheck that and recheck Microsoft Office 9.0 Object Library. Is there anyway to handle this with code? TIA Nelson . |
#5
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Nelson,
The final version should use Create not -- HTH Bob Phillips ... looking out across Poole Harbour to the Purbecks (remove nothere from the email address if mailing direct) wrote in message ... I copied the code from the url you provided. Having problems: If remove the Outlook reference, I get a compile error User Defined Type not Defined on Set objOutlook = New Outlook.Application If I keep the Outlook reference I get a syntax error on Set objRecipient.add("Hicks, Nelson") -----Original Message----- Nelson, use late binding. Here's a link to an Outlook example of converting from early to late binding that I gave earlier this year http://tinyurl.com/yhls -- HTH Bob Phillips ... looking out across Poole Harbour to the Purbecks (remove nothere from the email address if mailing direct) "Nelson" wrote in message ... I have Excel files that are used by people with different version of MS Office. These files create an Outlook object and send emails. The issue is, when a person with Outlook 2002 uses the file, Excel is smart enough to switch to the Microsoft Office 10.0 Object Library. However, next next person with Outlook 2000 receives compile errors when the Excel code runs. When I look at the references, it shows, MISSING Microsoft Office 10.0 Object Library. I have to uncheck that and recheck Microsoft Office 9.0 Object Library. Is there anyway to handle this with code? TIA Nelson . |
#6
![]()
Posted to microsoft.public.excel.programming
|
|||
|
|||
![]()
Thanks, made 2 changes.
Set objOutlook = CreateObject("Outlook.Application") Set objRecipient = objMailItem.Recipients.Add("Last, First") -----Original Message----- Nelson, The final version should use Create not -- HTH Bob Phillips ... looking out across Poole Harbour to the Purbecks (remove nothere from the email address if mailing direct) wrote in message ... I copied the code from the url you provided. Having problems: If remove the Outlook reference, I get a compile error User Defined Type not Defined on Set objOutlook = New Outlook.Application If I keep the Outlook reference I get a syntax error on Set objRecipient.add("Hicks, Nelson") -----Original Message----- Nelson, use late binding. Here's a link to an Outlook example of converting from early to late binding that I gave earlier this year http://tinyurl.com/yhls -- HTH Bob Phillips ... looking out across Poole Harbour to the Purbecks (remove nothere from the email address if mailing direct) "Nelson" wrote in message ... I have Excel files that are used by people with different version of MS Office. These files create an Outlook object and send emails. The issue is, when a person with Outlook 2002 uses the file, Excel is smart enough to switch to the Microsoft Office 10.0 Object Library. However, next next person with Outlook 2000 receives compile errors when the Excel code runs. When I look at the references, it shows, MISSING Microsoft Office 10.0 Object Library. I have to uncheck that and recheck Microsoft Office 9.0 Object Library. Is there anyway to handle this with code? TIA Nelson . . |
Reply |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Forum | |||
Help with Object Library | Setting up and Configuration of Excel | |||
missing object library | Excel Discussion (Misc queries) | |||
Object library missing | Excel Discussion (Misc queries) | |||
Problem with the Excel 10.0 Object Library | Excel Programming | |||
'Object library not registered' in Excel97 | Excel Programming |