How to determine the Service Pack level?

Hi everyone-

My app is running into some bugs with Office 2000 users who
haven't installed Service Pack 3, as described in
Microsoft's knowledge base article # 254714:
http://support.microsoft.com/?kbid=254714 . I know it's
hard to believe that they're that far behind, but...

Does anyone know how I can programmatically read the
installed Service Pack level at runtime, so I can have my
app quit, or at least notify the user, if the user doesn't
have at least SP3 of Office 2000?

I thought perhaps this info was in the
Outlook.Application.Version property, but I don't know how
to decipher the build numbers if the info is, in fact, there.

I have no problem with reading it from a Registry key, as
long as I know WHICH key, and how to interpret the data!


Thanks,


-Andrew

See http://www.slipstick.com/outlook/ol2000.htm#versions for the build
numbers

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


"Andrew Cushen" <anonymous@discussions.microsoft.com> wrote in message
news:082401c4c6b8$a53e4460$3501280a@phx.gbl...
> Hi everyone-
>
> My app is running into some bugs with Office 2000 users who
> haven't installed Service Pack 3, as described in
> Microsoft's knowledge base article # 254714:
> http://support.microsoft.com/?kbid=254714 . I know it's
> hard to believe that they're that far behind, but...
>
> Does anyone know how I can programmatically read the
> installed Service Pack level at runtime, so I can have my
> app quit, or at least notify the user, if the user doesn't
> have at least SP3 of Office 2000?
>
> I thought perhaps this info was in the
> Outlook.Application.Version property, but I don't know how
> to decipher the build numbers if the info is, in fact, there.
>
> I have no problem with reading it from a Registry key, as
> long as I know WHICH key, and how to interpret the data!
>
>
> Thanks,
>
>
> -Andrew

Thanks, Sue! I had tried a search on your site
for "Service Packs" and came up blank...but I should have
looked for "Build Numbers", I guess.

So I take it there's no other way to get the Service Pack
numbers, other than parsing them out of the build
numbers? That doesn't bode well for my app when future
versions of Outlook come out...but I guess I can handle
that when I get there...

Does the above hold true for outlook 2002 and 2003 as
well? Or is there a better way?

TIA,

-Andrew
=================================================
>-----Original Message-----
>See http://www.slipstick.com/outlook/ol2000.htm#versions
for the build
>numbers
>
>--
>Sue Mosher, Outlook MVP
>Author of
> Microsoft Outlook Programming - Jumpstart for
> Administrators, Power Users, and Developers
> http://www.outlookcode.com/jumpstart.aspx
>
>
>"Andrew Cushen" <anonymous@discussions.microsoft.com>
wrote in message
>news:082401c4c6b8$a53e4460$3501280a@phx.gbl...
>> Hi everyone-
>>
>> My app is running into some bugs with Office 2000
users who
>> haven't installed Service Pack 3, as described in
>> Microsoft's knowledge base article # 254714:
>> http://support.microsoft.com/?kbid=254714 . I know it's
>> hard to believe that they're that far behind, but...
>>
>> Does anyone know how I can programmatically read the
>> installed Service Pack level at runtime, so I can have
my
>> app quit, or at least notify the user, if the user
doesn't
>> have at least SP3 of Office 2000?
>>
>> I thought perhaps this info was in the
>> Outlook.Application.Version property, but I don't know
how
>> to decipher the build numbers if the info is, in fact,
there.
>>
>> I have no problem with reading it from a Registry key,
as
>> long as I know WHICH key, and how to interpret the
data!
>>
>>
>> Thanks,
>>
>>
>> -Andrew
>
>
>.
>

In all versions of Outlook, in order to know the SP level, you need to know
the build number.

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


"Andrew Cushen" <anonymous@discussions.microsoft.com> wrote in message
news:573d01c4c837$0f69e090$a601280a@phx.gbl...
> Thanks, Sue! I had tried a search on your site
> for "Service Packs" and came up blank...but I should have
> looked for "Build Numbers", I guess.
>
> So I take it there's no other way to get the Service Pack
> numbers, other than parsing them out of the build
> numbers? That doesn't bode well for my app when future
> versions of Outlook come out...but I guess I can handle
> that when I get there...
>
> Does the above hold true for outlook 2002 and 2003 as
> well? Or is there a better way?
>
> TIA,
>
> -Andrew
> =================================================
>>-----Original Message-----
>>See http://www.slipstick.com/outlook/ol2000.htm#versions
> for the build
>>numbers
>>
>>"Andrew Cushen" <anonymous@discussions.microsoft.com>
> wrote in message
>>news:082401c4c6b8$a53e4460$3501280a@phx.gbl...
>>> Hi everyone-
>>>
>>> My app is running into some bugs with Office 2000
> users who
>>> haven't installed Service Pack 3, as described in
>>> Microsoft's knowledge base article # 254714:
>>> http://support.microsoft.com/?kbid=254714 . I know it's
>>> hard to believe that they're that far behind, but...
>>>
>>> Does anyone know how I can programmatically read the
>>> installed Service Pack level at runtime, so I can have
> my
>>> app quit, or at least notify the user, if the user
> doesn't
>>> have at least SP3 of Office 2000?
>>>
>>> I thought perhaps this info was in the
>>> Outlook.Application.Version property, but I don't know
> how
>>> to decipher the build numbers if the info is, in fact,
> there.
>>>
>>> I have no problem with reading it from a Registry key,
> as
>>> long as I know WHICH key, and how to interpret the
> data!
>>>
>>>
>>> Thanks,
>>>
>>>
>>> -Andrew
>>
>>
>>.
>>

OK, Thanks, Sue.

Back to the grindstone...


-Andrew
=============================================
>-----Original Message-----
>In all versions of Outlook, in order to know the SP
level, you need to know
>the build number.
>
>--
>Sue Mosher, Outlook MVP
>Author of
> Microsoft Outlook Programming - Jumpstart for
> Administrators, Power Users, and Developers
> http://www.outlookcode.com/jumpstart.aspx
>
>
>"Andrew Cushen" <anonymous@discussions.microsoft.com>
wrote in message
>news:573d01c4c837$0f69e090$a601280a@phx.gbl...
>> Thanks, Sue! I had tried a search on your site
>> for "Service Packs" and came up blank...but I should
have
>> looked for "Build Numbers", I guess.
>>
>> So I take it there's no other way to get the Service
Pack
>> numbers, other than parsing them out of the build
>> numbers? That doesn't bode well for my app when future
>> versions of Outlook come out...but I guess I can handle
>> that when I get there...
>>
>> Does the above hold true for outlook 2002 and 2003 as
>> well? Or is there a better way?
>>
>> TIA,
>>
>> -Andrew
>> =================================================
>>>-----Original Message-----
>>>See
http://www.slipstick.com/outlook/ol2000.htm#versions
>> for the build
>>>numbers
>>>
>>>"Andrew Cushen" <anonymous@discussions.microsoft.com>
>> wrote in message
>>>news:082401c4c6b8$a53e4460$3501280a@phx.gbl...
>>>> Hi everyone-
>>>>
>>>> My app is running into some bugs with Office 2000
>> users who
>>>> haven't installed Service Pack 3, as described in
>>>> Microsoft's knowledge base article # 254714:
>>>> http://support.microsoft.com/?kbid=254714 . I know
it's
>>>> hard to believe that they're that far behind, but...
>>>>
>>>> Does anyone know how I can programmatically read the
>>>> installed Service Pack level at runtime, so I can
have
>> my
>>>> app quit, or at least notify the user, if the user
>> doesn't
>>>> have at least SP3 of Office 2000?
>>>>
>>>> I thought perhaps this info was in the
>>>> Outlook.Application.Version property, but I don't
know
>> how
>>>> to decipher the build numbers if the info is, in
fact,
>> there.
>>>>
>>>> I have no problem with reading it from a Registry
key,
>> as
>>>> long as I know WHICH key, and how to interpret the
>> data!
>>>>
>>>>
>>>> Thanks,
>>>>
>>>>
>>>> -Andrew
>>>
>>>
>>>.
>>>
>
>
>.
>