Office 14.2.0 is not updated - KB Article for database rebuild
Peter, actually it looks like the update was applied. Notice under the Word version in your screen shot that it states the latest installed update is 14.2.0. That is why the update fails to find an office to update.
However, your update does not appear to have completed correctly.
1) Do you remember anything going awry the first time you ran the update? Need to turn off your machine? Install say it failed?
2) I would like to look at the install log from the first install (you can choose to post it so others can troubleshoot if they see similar problems or you can choose to send it to me as a private message) so we can find the root of the problem so you don't run into this again. To access the old install log...
a) launch Console
b) click the show log list button (top left corner)
c) display the install logs (from the disclosure list on the left choose Files | /private/var/Log | install.log
d) you are looking through the list (should be quick to find) for when you first installed the update - select that through the end of the file and copy that into a reply or a mail to me.
3) unfortunately you will need to reinstall. There is no re-apply functionality to the updater. I am truly sorry about that - and that is why I want to see your install log, because if something is going on during your update I don't want you to hit it again and be in this same boat.
To reinstall, just drag the Office 2011 folder to the trash and then start your install - no need to kill preferences or anything else. Once the install is complete, since you had AutoUpdate on already, it should bring it up and offer you the updates. If it doesn't, you can manually launch AutoUpdate (/Library/Application Support/Microsoft/MAU 2.0/
I am sorry this happened to you
David
----------
For those of you needing to rebuild the database (alert saying "
Your identity is older than this version of Outlook. Please rebuild by using the last version of Outlook that used this identity."), you can find the KB article describing a workaround here:
http://support.microsoft.com/kb/2702740
David