I'd like to be able to run a bit of code on all of my user's workstations to
determine if SP2 is installed. I'm pretty much open to any method that works.

TIA

Doug

Application.Build

This is the Build's I have for my 2007 SP1 & SP2 respectively
6331, 6524

My guess is if it's say 6500+ you can be pretty sure it's SP2 (in 2007 of
course), but I'll leave it to you to research if that is indeed the case.
Maybe you might post back your findings!

Regards,
Peter T



"Doug_F" <(E-Mail Removed)> wrote in message
news:5D365754-FD4C-4FDB-BEB0-(E-Mail Removed)...
> I'd like to be able to run a bit of code on all of my user's workstations
> to
> determine if SP2 is installed. I'm pretty much open to any method that
> works.
>
> TIA
>
> Doug

Peter,

Thanks. Off to write some code and trap some data.

Doug

"Peter T" wrote:

> Application.Build
>
> This is the Build's I have for my 2007 SP1 & SP2 respectively
> 6331, 6524
>
> My guess is if it's say 6500+ you can be pretty sure it's SP2 (in 2007 of
> course), but I'll leave it to you to research if that is indeed the case.
> Maybe you might post back your findings!
>
> Regards,
> Peter T
>
>
>
> "Doug_F" <(E-Mail Removed)> wrote in message
> news:5D365754-FD4C-4FDB-BEB0-(E-Mail Removed)...
> > I'd like to be able to run a bit of code on all of my user's workstations
> > to
> > determine if SP2 is installed. I'm pretty much open to any method that
> > works.
> >
> > TIA
> >
> > Doug
>
>
> .
>

Interesting observation. I agree the first set of 4 digits correlates to the
Build number.

FWIW I hadn't suggested 6500 was the lower limit, rather as a guess above
that probably confirms SP2, not quite the same thing. However I am now
starting to wonder if the build number even relates to the SP at all, maybe
it doesn't!

Regards,
Peter T

"Cosmo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> I have a similar need, and I found this thread (and forum) in my
> search. On the computers I have checked in my office, I am getting 2
> different numbers for SP2
>
> 12.0.6425.1000 SP2
> 12.0.6504.5000 SP2
>
> The first set of 4 digits after the version number (12.0) correlates to
> the Build number; don't know what the last set of 4 digits signifies.
>
> Has anyone resolved how to determine which numbers (or number range)
> distinguishes SP1 from SP2? Since I'm getting 6425, it would appear that
> 6500 is not the lower limit for SP2 as has been suggested here.
>
>
> Doug_F;645959 Wrote:
>>
> Peter,
>>
>> Thanks. Off to write some code and trap some data.
>>
>> Doug
>>
>> "Peter T" wrote:
>>
>> > Application.Build
>> >
>> > This is the Build's I have for my 2007 SP1 & SP2 respectively
>> > 6331, 6524
>> >
>> > My guess is if it's say 6500+ you can be pretty sure it's SP2 (in
> 2007 of
>> > course), but I'll leave it to you to research if that is indeed the
> case.
>> > Maybe you might post back your findings!
>> >
>> > Regards,
>> > Peter T
>> >
>> >
>> >
>> > "Doug_F" <(E-Mail Removed)> wrote in message
>> > news:5D365754-FD4C-4FDB-BEB0-(E-Mail Removed)...
>> > > I'd like to be able to run a bit of code on all of my user's
> workstations
>> > > to
>> > > determine if SP2 is installed. I'm pretty much open to any method
> that
>> > > works.
>> > >
>> > > TIA
>> > >
>> > > Doug
>> >
>> >
>> > .
>> >
>
>
> --
> Cosmo
> ------------------------------------------------------------------------
> Cosmo's Profile: 1576
> View this thread:
> http://www.thecodecage.com/forumz/sh...d.php?t=179767
>
> Microsoft Office Help
>

From your posts and thinking about it more it really seems that app.Build
does not help determine which SP is installed, sorry for introducing the
idea. It got me to thinking along different lines.

In the main SP2 fixes and improves things. However here's an odd bug which,
in limited testing, appears to have been introduced in SP2

=DATEDIF(DATE(2009,6,27),DATE(2012,1,5),"md")

If you get the "wrong" answer 122 it's probably SP2, but if you get the
right answer of 9 it's probably SP1.

Please (anyone) feel free to confirm or otherwise. I'm sure there are other
discrepancies which might be similarly checked but off the top of my head
forget which.

Regards,
Peter T

"Cosmo" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>
> Sorry, didn't mean to imply that the suggestion was based on more than
> a guess, should have said something more along the lines of 'as has been
> suggested might be the case'
>
> A little more investigating in my office showed a few other details:
> I've been checking the Resources panel in PowerPoint and I have found a
> few machines that show different results:
>
> My computer and another I checked shows both sets of numbers the same:
> Microsoft Office PowerPoint 2007 (12.0.6425.1000) SP2 MSO
> (12.0.6425.1000)
> These numbers are the same in Excel and Word as well.
>
> On a few computers, the two sets of numbers are different:
> Microsoft Office PowerPoint 2007 (12.0.6504.5000) SP2 MSO
> (12.0.6425.1000)
> Microsoft Office Excel 2007 (12.0.6514.5000) SP2 MSO (12.0.6425.1000)
> The number which corresponds with the 'Application.Build' is the first
> set of 4 digits in the first group of numbers (before the 'SP2'), and is
> different for each Office application.
>
> I wish I knew if this number has any correlation to the SP number; I
> feel like I'm making some slight progress, but can't tell if I'm
> actually getting anywhere. And I haven't found anywhere that explains
> what these numbers mean, and why they are not consistent across our
> systems.
>
> Peter T;661204 Wrote:
>>
> Interesting observation. I agree the first set of 4 digits correlates
> to the
>> Build number.
>>
>> FWIW I hadn't suggested 6500 was the lower limit, rather as a guess
> above
>> that probably confirms SP2, not quite the same thing. However I am now
>> starting to wonder if the build number even relates to the SP at all,
> maybe
>> it doesn't!
>>
>> Regards,
>> Peter T
>>
>> "Cosmo" <(E-Mail Removed)> wrote in message
>> news:(E-Mail Removed)...
>> >
>> > I have a similar need, and I found this thread (and forum) in my
>> > search. On the computers I have checked in my office, I am getting 2
>> > different numbers for SP2
>> >
>> > 12.0.6425.1000 SP2
>> > 12.0.6504.5000 SP2
>> >
>> > The first set of 4 digits after the version number (12.0) correlates
> to
>> > the Build number; don't know what the last set of 4 digits
> signifies.
>> >
>> > Has anyone resolved how to determine which numbers (or number range)
>> > distinguishes SP1 from SP2? Since I'm getting 6425, it would appear
> that
>> > 6500 is not the lower limit for SP2 as has been suggested here.
>> >
>> >
>> > Doug_F;645959 Wrote:
>> >>
>> > Peter,
>> >>
>> >> Thanks. Off to write some code and trap some data.
>> >>
>> >> Doug
>> >>
>> >> "Peter T" wrote:
>> >>
>> >> > Application.Build
>> >> >
>> >> > This is the Build's I have for my 2007 SP1 & SP2 respectively
>> >> > 6331, 6524
>> >> >
>> >> > My guess is if it's say 6500+ you can be pretty sure it's SP2 (in
>> > 2007 of
>> >> > course), but I'll leave it to you to research if that is indeed
> the
>> > case.
>> >> > Maybe you might post back your findings!
>> >> >
>> >> > Regards,
>> >> > Peter T
>> >> >
>> >> >
>> >> >
>> >> > "Doug_F" <(E-Mail Removed)> wrote in message
>> >> > news:5D365754-FD4C-4FDB-BEB0-(E-Mail Removed)...
>> >> > > I'd like to be able to run a bit of code on all of my user's
>> > workstations
>> >> > > to
>> >> > > determine if SP2 is installed. I'm pretty much open to any
> method
>> > that
>> >> > > works.
>> >> > >
>> >> > > TIA
>> >> > >
>> >> > > Doug
>> >> >
>> >> >
>> >> > .
>> >> >
>> >
>> >
>> > --
>> > Cosmo
>> >
> ------------------------------------------------------------------------
>> > Cosmo's Profile: 1576
>> > View this thread:
>> > 'Any way to determine Service Pack level on an Excel install - The
> Code Cage Forums'
> (http://www.thecodecage.com/forumz/sh...d.php?t=179767)
>> >
>> > 'Microsoft Office Help' (&quot;http://www.thecodecage.com&quot;)
>> >
>
>
> --
> Cosmo
> ------------------------------------------------------------------------
> Cosmo's Profile: 1576
> View this thread:
> http://www.thecodecage.com/forumz/sh...d.php?t=179767
>
> Microsoft Office Help
>

Oh man, this just gets better and better.

I wrote a bit of code that eventually does 'xlApp.Build' and sent it around
for folks to run and log the results into a database.

I have a user who shows the following:
If he looks in Excel at the resources to get the version and build we see:
2007 (12.0.6504.5000) SP2 MSO ( 12.0.6425.1000)
When he runs my little script, I get version 12 and build 6514.

WT#$&&??

I ran into the same problem with a different user, the 'build' after MSO was
something like 6020 but xlApp.Build was 4518.

Does anyone have any idea which way to go?

I guess for us, it may not really matter. We're supposed to be using
software delivery system that pushes the SAME version to EVERYONE. The fact
that we're seeing 4 or 5 different builds may mean that the push software
isn't working as expected or IT has mucked up the package and is pushing
different version which would be out of compliance with our change control
procedures.

I'd like to have some resolution before I start screaming at IT...

Thanks

"Cosmo" wrote:

>
> Sorry, didn't mean to imply that the suggestion was based on more than
> a guess, should have said something more along the lines of 'as has been
> suggested might be the case'
>
> A little more investigating in my office showed a few other details:
> I've been checking the Resources panel in PowerPoint and I have found a
> few machines that show different results:
>
> My computer and another I checked shows both sets of numbers the same:
> Microsoft Office PowerPoint 2007 (12.0.6425.1000) SP2 MSO
> (12.0.6425.1000)
> These numbers are the same in Excel and Word as well.
>
> On a few computers, the two sets of numbers are different:
> Microsoft Office PowerPoint 2007 (12.0.6504.5000) SP2 MSO
> (12.0.6425.1000)
> Microsoft Office Excel 2007 (12.0.6514.5000) SP2 MSO (12.0.6425.1000)
> The number which corresponds with the 'Application.Build' is the first
> set of 4 digits in the first group of numbers (before the 'SP2'), and is
> different for each Office application.
>
> I wish I knew if this number has any correlation to the SP number; I
> feel like I'm making some slight progress, but can't tell if I'm
> actually getting anywhere. And I haven't found anywhere that explains
> what these numbers mean, and why they are not consistent across our
> systems.
>
>
Peter T;661204 Wrote:
> >
> Interesting observation. I agree the first set of 4 digits correlates
> to the
> > Build number.
> >
> > FWIW I hadn't suggested 6500 was the lower limit, rather as a guess
> above
> > that probably confirms SP2, not quite the same thing. However I am now
> > starting to wonder if the build number even relates to the SP at all,
> maybe
> > it doesn't!
> >
> > Regards,
> > Peter T
> >
> > "Cosmo" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed)...
> > >
> > > I have a similar need, and I found this thread (and forum) in my
> > > search. On the computers I have checked in my office, I am getting 2
> > > different numbers for SP2
> > >
> > > 12.0.6425.1000 SP2
> > > 12.0.6504.5000 SP2
> > >
> > > The first set of 4 digits after the version number (12.0) correlates
> to
> > > the Build number; don't know what the last set of 4 digits
> signifies.
> > >
> > > Has anyone resolved how to determine which numbers (or number range)
> > > distinguishes SP1 from SP2? Since I'm getting 6425, it would appear
> that
> > > 6500 is not the lower limit for SP2 as has been suggested here.
> > >
> > >
> > > Doug_F;645959 Wrote:
> > >>
> > > Peter,
> > >>
> > >> Thanks. Off to write some code and trap some data.
> > >>
> > >> Doug
> > >>
> > >> "Peter T" wrote:
> > >>
> > >> > Application.Build
> > >> >
> > >> > This is the Build's I have for my 2007 SP1 & SP2 respectively
> > >> > 6331, 6524
> > >> >
> > >> > My guess is if it's say 6500+ you can be pretty sure it's SP2 (in
> > > 2007 of
> > >> > course), but I'll leave it to you to research if that is indeed
> the
> > > case.
> > >> > Maybe you might post back your findings!
> > >> >
> > >> > Regards,
> > >> > Peter T
> > >> >
> > >> >
> > >> >
> > >> > "Doug_F" <(E-Mail Removed)> wrote in message
> > >> > news:5D365754-FD4C-4FDB-BEB0-(E-Mail Removed)...
> > >> > > I'd like to be able to run a bit of code on all of my user's
> > > workstations
> > >> > > to
> > >> > > determine if SP2 is installed. I'm pretty much open to any
> method
> > > that
> > >> > > works.
> > >> > >
> > >> > > TIA
> > >> > >
> > >> > > Doug
> > >> >
> > >> >
> > >> > .
> > >> >
> > >
> > >
> > > --
> > > Cosmo
> > >
> ------------------------------------------------------------------------
> > > Cosmo's Profile: 1576
> > > View this thread:
> > > 'Any way to determine Service Pack level on an Excel install - The
> Code Cage Forums'
> (http://www.thecodecage.com/forumz/sh...d.php?t=179767)
> > >
> > > 'Microsoft Office Help' ("http://www.thecodecage.com")
> > >
>
>
> --
> Cosmo
> ------------------------------------------------------------------------
> Cosmo's Profile: 1576
> View this thread: http://www.thecodecage.com/forumz/sh...d.php?t=179767
>
> Microsoft Office Help
>
> .
>

Turns out, he did the 'resource' check using Word and my code checks Excel.
I'm betting when he tests again in Excel, it will show 6514.

I just checked with my 6020/4518 guy and the 4518 is on the 'left' side and
the 6020 is on the 'right' side, so xl.Build is pulling in data from the left
parenthetical number set.

On my machine (which is at SP2), I show 6525 in both sets of numbers.

So does this help at all? Can I relate any 'build' value with SP2 or is
this a lost cause?

Doug

"Doug_F" wrote:

> I have a user who shows the following:
> If he looks in Excel at the resources to get the version and build we see:
> 2007 (12.0.6504.5000) SP2 MSO ( 12.0.6425.1000)
> When he runs my little script, I get version 12 and build 6514.
>
> WT#$&&??
>

I know my first idea wasn't very good, but don't let that put you off trying
my latest!

in VBA
x = Application.Evaluate("=DATEDIF(DATE(2009,6,27),DATE(2012,1,5),""md"")")

If x = 9 then
sp = 1
elseif x = 122 then
sp = 2

Like I say, only an idea. Maybe you and Cosmo might check it out with your
combination of SP1 & SP2 users....

Regards,
Peter T

"Doug_F" <(E-Mail Removed)> wrote in message
news:2DE0A676-0187-455B-A711-(E-Mail Removed)...
> Oh man, this just gets better and better.
>
> I wrote a bit of code that eventually does 'xlApp.Build' and sent it
> around
> for folks to run and log the results into a database.
>
> I have a user who shows the following:
> If he looks in Excel at the resources to get the version and build we see:
> 2007 (12.0.6504.5000) SP2 MSO ( 12.0.6425.1000)
> When he runs my little script, I get version 12 and build 6514.
>
> WT#$&&??
>
> I ran into the same problem with a different user, the 'build' after MSO
> was
> something like 6020 but xlApp.Build was 4518.
>
> Does anyone have any idea which way to go?
>
> I guess for us, it may not really matter. We're supposed to be using
> software delivery system that pushes the SAME version to EVERYONE. The
> fact
> that we're seeing 4 or 5 different builds may mean that the push software
> isn't working as expected or IT has mucked up the package and is pushing
> different version which would be out of compliance with our change control
> procedures.
>
> I'd like to have some resolution before I start screaming at IT...
>
> Thanks
>
> "Cosmo" wrote:
>
>>
>> Sorry, didn't mean to imply that the suggestion was based on more than
>> a guess, should have said something more along the lines of 'as has been
>> suggested might be the case'
>>
>> A little more investigating in my office showed a few other details:
>> I've been checking the Resources panel in PowerPoint and I have found a
>> few machines that show different results:
>>
>> My computer and another I checked shows both sets of numbers the same:
>> Microsoft Office PowerPoint 2007 (12.0.6425.1000) SP2 MSO
>> (12.0.6425.1000)
>> These numbers are the same in Excel and Word as well.
>>
>> On a few computers, the two sets of numbers are different:
>> Microsoft Office PowerPoint 2007 (12.0.6504.5000) SP2 MSO
>> (12.0.6425.1000)
>> Microsoft Office Excel 2007 (12.0.6514.5000) SP2 MSO (12.0.6425.1000)
>> The number which corresponds with the 'Application.Build' is the first
>> set of 4 digits in the first group of numbers (before the 'SP2'), and is
>> different for each Office application.
>>
>> I wish I knew if this number has any correlation to the SP number; I
>> feel like I'm making some slight progress, but can't tell if I'm
>> actually getting anywhere. And I haven't found anywhere that explains
>> what these numbers mean, and why they are not consistent across our
>> systems.
>>
>>
> Peter T;661204 Wrote:
>> >
>> Interesting observation. I agree the first set of 4 digits correlates
>> to the
>> > Build number.
>> >
>> > FWIW I hadn't suggested 6500 was the lower limit, rather as a guess
>> above
>> > that probably confirms SP2, not quite the same thing. However I am now
>> > starting to wonder if the build number even relates to the SP at all,
>> maybe
>> > it doesn't!
>> >
>> > Regards,
>> > Peter T
>> >
>> > "Cosmo" <(E-Mail Removed)> wrote in message
>> > news:(E-Mail Removed)...
>> > >
>> > > I have a similar need, and I found this thread (and forum) in my
>> > > search. On the computers I have checked in my office, I am getting 2
>> > > different numbers for SP2
>> > >
>> > > 12.0.6425.1000 SP2
>> > > 12.0.6504.5000 SP2
>> > >
>> > > The first set of 4 digits after the version number (12.0) correlates
>> to
>> > > the Build number; don't know what the last set of 4 digits
>> signifies.
>> > >
>> > > Has anyone resolved how to determine which numbers (or number range)
>> > > distinguishes SP1 from SP2? Since I'm getting 6425, it would appear
>> that
>> > > 6500 is not the lower limit for SP2 as has been suggested here.
>> > >
>> > >
>> > > Doug_F;645959 Wrote:
>> > >>
>> > > Peter,
>> > >>
>> > >> Thanks. Off to write some code and trap some data.
>> > >>
>> > >> Doug
>> > >>
>> > >> "Peter T" wrote:
>> > >>
>> > >> > Application.Build
>> > >> >
>> > >> > This is the Build's I have for my 2007 SP1 & SP2 respectively
>> > >> > 6331, 6524
>> > >> >
>> > >> > My guess is if it's say 6500+ you can be pretty sure it's SP2 (in
>> > > 2007 of
>> > >> > course), but I'll leave it to you to research if that is indeed
>> the
>> > > case.
>> > >> > Maybe you might post back your findings!
>> > >> >
>> > >> > Regards,
>> > >> > Peter T
>> > >> >
>> > >> >
>> > >> >
>> > >> > "Doug_F" <(E-Mail Removed)> wrote in message
>> > >> > news:5D365754-FD4C-4FDB-BEB0-(E-Mail Removed)...
>> > >> > > I'd like to be able to run a bit of code on all of my user's
>> > > workstations
>> > >> > > to
>> > >> > > determine if SP2 is installed. I'm pretty much open to any
>> method
>> > > that
>> > >> > > works.
>> > >> > >
>> > >> > > TIA
>> > >> > >
>> > >> > > Doug
>> > >> >
>> > >> >
>> > >> > .
>> > >> >
>> > >
>> > >
>> > > --
>> > > Cosmo
>> > >
>> ------------------------------------------------------------------------
>> > > Cosmo's Profile: 1576
>> > > View this thread:
>> > > 'Any way to determine Service Pack level on an Excel install - The
>> Code Cage Forums'
>> (http://www.thecodecage.com/forumz/sh...d.php?t=179767)
>> > >
>> > > 'Microsoft Office Help' ("http://www.thecodecage.com")
>> > >
>>
>>
>> --
>> Cosmo
>> ------------------------------------------------------------------------
>> Cosmo's Profile: 1576
>> View this thread:
>> http://www.thecodecage.com/forumz/sh...d.php?t=179767
>>
>> Microsoft Office Help
>>
>> .
>>

Oh, this is cool.

If I paste the formula below into an Excel cell, I get 173.

When I try and look up DateDif in excel Help, it doesn't exist.

If '9' is the right answer, and SP2 gives 122, what the heck do I have?

I'm really glad it's Friday.

In the main SP2 fixes and improves things. However here's an odd bug which,
in limited testing, appears to have been introduced in SP2

=DATEDIF(DATE(2009,6,27),DATE(2012,1,5),"md")

OK forget that idea then (fwiw the correct answer is 9, but DateDif is
buggy)

As I said before, I'm almost sure there are other differences in behaviour
between SP1 & SP2 that would help identify, just don't recall at the moment.

Regards,
Peter T

"Doug_F" <(E-Mail Removed)> wrote in message
newsF2A2D15-D4A3-4AA3-A4AB-(E-Mail Removed)...
> Oh, this is cool.
>
> If I paste the formula below into an Excel cell, I get 173.
>
> When I try and look up DateDif in excel Help, it doesn't exist.
>
> If '9' is the right answer, and SP2 gives 122, what the heck do I have?
>
> I'm really glad it's Friday.
>
> In the main SP2 fixes and improves things. However here's an odd bug
> which,
> in limited testing, appears to have been introduced in SP2
>
> =DATEDIF(DATE(2009,6,27),DATE(2012,1,5),"md")
>