BCM and SBA Service Pack 2 Confusions

[-]

I am running SBA 2006 and the latest version of BCM. If I manually check
for an update via the drop down menu in SBA 2006 right now, it will take me
to this update page:

http://www.microsoft.com/downloads/...AC-37F3-4EE1-931B-807703037E89&displaylang=en



"Service Pack 1 for Business Contact Manager Update and Small Business
Accounting"



File Name: OfficeSBMESP1-KB902963-FullFile-ENU.EXE

Version: 1.0

Date Published: 1/20/2006

Language: English

Download Size: 42.4 MB



That looks like SP1 to me (which I already have installed months ago).
Notice the date, version number and size of the file though.



Now, if I manually go to a link posted tonight for an update to SP2 found on
the Yahoo SBA list:



http://www.microsoft.com/downloads/...05-568b-41b0-9f45-045876cbe9a3&displaylang=en



"Service Pack 2 for Business Contact Manager Update and Small Business
Accounting"



File Name: OfficeSBMESP2-KB911051-FullFile-ENU.EXE

Version: 1.0

Date Published: 1/20/2006

Language: English

Download Size: 42.4 MB



Notice how the file size is the same, the date is the same and the version
number is 1.0. Unfortunately, the link on this page which is supposed to
take you to a page with a description of changes and upgrades does not work.



These two downloads certainly have different file names but I just wondered
why when I go to manually update it points me to SP1. Also, Microsoft
Update which checks for Windows and Office Updates does not show an update
to be available.



Can anyone confirm that the SP2 is a valid update? Any idea what it
corrects or improves?



Thanks!

 

[Chris Schatte]

-,
If your running sp1 your should recieve the prompt to upgrade your db.

Chris Schatte

 

[Chris Schatte]

Too add, when using SBA Help about your version should read sp2 with the
appropriate version number.

Chris Schatte

 

[Luther]

Microsoft marketing's naming of their packages is very confusing, even
to those of use that have been using BCM and SBA since they were first
released. That's one reason on the newgroup we tend to refer to them by
version numbers (right click on a DLL and examine the properties, or
check the About window of the applications). That, of course, is no
help when you're looking at their web pages and trying to figure out
what a package actually contains.