OS v. applications ... and more on Office 12 (2007) and OpenXML ...
Now with that said, understand Office 12 (2007) is Microsoft's first attempt at a real portable codebase for Office.
All current MS Office for Mac releases are non-native, heavily hacked, from their initial Windows release.
Microsoft has had to change how Office 12 works for future portability (e.g., 64-bit).
All prior version of Office had nasty histories of binary incompatibility, largely because the formats changed slightly between releases.
A lot of this had to do with the codebase, ignoring data alignment (which is allowed on 16/32-bit x86, but not other processors like the Mac's PowerPC, nor x86-64 for that matter), etc...
To this end, MS Office 12 now encodes everything into XML formats, which Microsoft calls OpenXML.
It's a long story to explain, but understand XML is not an "open, end-user" standard, it's a standard for creating vendor-centric standards.
OpenXML is largely being used to encode and encapsulate existing binary objects for Office meta-data (seemingly Base64 from what I've seen).
That makes the format portable and much longer lasting, between versions.
But "OpenXML" itself is hardly an "open" standard, and has many IP strings attached.
In comparison, everyone from IBM to Novell to Sun, and major users like Boeing (the US' #1 exporter) to several US states use Open Document Format (ODF) XML.
All of ODF's IP has been signed over to the OASIS, which is the industry defacto standard organization for XML publication.
Microsoft's ********** to the EMCA does not cover IP issues, and it doesn't document Microsoft's encapsulation of encoded binary objects (which still make up most of the meta-data in MS Office 12 formats).
Now MS Office 12 (2007) actually handles legacy Office 8/9/10/11 (97/2000/XP-2002/2003) decently, at least newer 10 and 11 versions (XP-2002 and 2003).
I am now personally running MS Word 12 (2007) myself, just got it yesterday, and it's doing fine with the Office 11 (2003) documents I threw at it, but barfed on an older version 9 (2000) document.
There are some conflicting tags between those older versions and newer versions.
If you have a lot of older MS Office 8, 9 or 10 (97, 2000 or XP-2002), let alone MS Office 6 or 7 (95), I highly recommend Corel PerfectOffice or OpenOffice.org/StarOffice.
They handle import/conversion/export much better than MS Office 12 (2007) or even 11 (2003), let alone Office 12 (2007) doesn't even do Office 6 or 7 (95) formats anymore.
Microsoft even used Sun (who owns all copyright to OpenOffice.org, and funds most of the developers on the project, who also write StarOffice) to develop many of the "Compatibility Mode" filters.
Sun has had a broad cross-patent/development license with Microsoft since 2003, which not even most in the Linux world realize (hence why the MS Office import/conversion filters in OpenOffice.org 2.0/StarOffice 8 for newer Office 11/2003 documents got even better).
StarOffice 9 (and most likely OpenOffice.org 3 as well, depending on the IP arguments) will support OpenXML.
Novell and Sun are working on the import/conversion filters, as they both have broad agreements with Microsoft.
As does Corel, who still makes a well respected word processing product that law and medical offices have used for over 20 years.
Document longevity is a big thing when it comes to such professions, as not being able to edit a format less than 10 years old is unacceptable, or losing formatting when it's not even 5 years old.
Hence why Boeing is even adopting ODF, and supported it's standardization.
BTW, I actually started using StarOffice 3.0 on Windows back in 1995, and can still read my documents perfectly in StarOffice 8 some 12 years later.
I adopted StarOffice back (mid-90s) then because I read Ami Pro 3 documents (Ami Pro was the best combination of desktop publishing, DTP, app and word processing in one).
I finally made my switch permanent with the new Office 8 (97) wouldn't read my Office 7 (95) templates and documents, or just destroyed formatting, so I gave up.
At the same time, I can pass those old StarOffice documents on to anyone with the free OpenOffice.org suite, as it reads them too, all the way back to those legacy formats.
Despite what people assume, OpenOffice.org/StarOffice actually have features MS Office does not, and StarOffice has for a long time.
E.g., HTML export and other feature were in it over 2 years before Microsoft finally added them to Office.
So the "good news" with Office 12 (2007) is that you're going to get better document longevity than before.
But the "bad news" is that it's still using a lot of binary data (only encoded/encapsulated in XML), so it's no less "open."

No one is a "computer whiz," people just have their experience -- and some experience in some areas more than others.Prof, I am no computer whiz,
Microsoft Windows Vista (NT version 6.0), the OS, and Microsoft Office 2007 (Office version 12), the application (or set of applications) aren't related other than timing in release.but do I understand it correctly that all the Excel (for example) databases will have to be manually re-written fro the new Vista/Office combo?
Now with that said, understand Office 12 (2007) is Microsoft's first attempt at a real portable codebase for Office.
All current MS Office for Mac releases are non-native, heavily hacked, from their initial Windows release.
Microsoft has had to change how Office 12 works for future portability (e.g., 64-bit).
All prior version of Office had nasty histories of binary incompatibility, largely because the formats changed slightly between releases.
A lot of this had to do with the codebase, ignoring data alignment (which is allowed on 16/32-bit x86, but not other processors like the Mac's PowerPC, nor x86-64 for that matter), etc...
To this end, MS Office 12 now encodes everything into XML formats, which Microsoft calls OpenXML.
It's a long story to explain, but understand XML is not an "open, end-user" standard, it's a standard for creating vendor-centric standards.
OpenXML is largely being used to encode and encapsulate existing binary objects for Office meta-data (seemingly Base64 from what I've seen).
That makes the format portable and much longer lasting, between versions.
But "OpenXML" itself is hardly an "open" standard, and has many IP strings attached.
In comparison, everyone from IBM to Novell to Sun, and major users like Boeing (the US' #1 exporter) to several US states use Open Document Format (ODF) XML.
All of ODF's IP has been signed over to the OASIS, which is the industry defacto standard organization for XML publication.
Microsoft's ********** to the EMCA does not cover IP issues, and it doesn't document Microsoft's encapsulation of encoded binary objects (which still make up most of the meta-data in MS Office 12 formats).
Now MS Office 12 (2007) actually handles legacy Office 8/9/10/11 (97/2000/XP-2002/2003) decently, at least newer 10 and 11 versions (XP-2002 and 2003).
I am now personally running MS Word 12 (2007) myself, just got it yesterday, and it's doing fine with the Office 11 (2003) documents I threw at it, but barfed on an older version 9 (2000) document.
There are some conflicting tags between those older versions and newer versions.
If you have a lot of older MS Office 8, 9 or 10 (97, 2000 or XP-2002), let alone MS Office 6 or 7 (95), I highly recommend Corel PerfectOffice or OpenOffice.org/StarOffice.
They handle import/conversion/export much better than MS Office 12 (2007) or even 11 (2003), let alone Office 12 (2007) doesn't even do Office 6 or 7 (95) formats anymore.
Microsoft even used Sun (who owns all copyright to OpenOffice.org, and funds most of the developers on the project, who also write StarOffice) to develop many of the "Compatibility Mode" filters.
Sun has had a broad cross-patent/development license with Microsoft since 2003, which not even most in the Linux world realize (hence why the MS Office import/conversion filters in OpenOffice.org 2.0/StarOffice 8 for newer Office 11/2003 documents got even better).
StarOffice 9 (and most likely OpenOffice.org 3 as well, depending on the IP arguments) will support OpenXML.
Novell and Sun are working on the import/conversion filters, as they both have broad agreements with Microsoft.
As does Corel, who still makes a well respected word processing product that law and medical offices have used for over 20 years.
Document longevity is a big thing when it comes to such professions, as not being able to edit a format less than 10 years old is unacceptable, or losing formatting when it's not even 5 years old.
Hence why Boeing is even adopting ODF, and supported it's standardization.
BTW, I actually started using StarOffice 3.0 on Windows back in 1995, and can still read my documents perfectly in StarOffice 8 some 12 years later.
I adopted StarOffice back (mid-90s) then because I read Ami Pro 3 documents (Ami Pro was the best combination of desktop publishing, DTP, app and word processing in one).
I finally made my switch permanent with the new Office 8 (97) wouldn't read my Office 7 (95) templates and documents, or just destroyed formatting, so I gave up.
At the same time, I can pass those old StarOffice documents on to anyone with the free OpenOffice.org suite, as it reads them too, all the way back to those legacy formats.
Despite what people assume, OpenOffice.org/StarOffice actually have features MS Office does not, and StarOffice has for a long time.
E.g., HTML export and other feature were in it over 2 years before Microsoft finally added them to Office.
So the "good news" with Office 12 (2007) is that you're going to get better document longevity than before.
But the "bad news" is that it's still using a lot of binary data (only encoded/encapsulated in XML), so it's no less "open."
Britney Swallows has a seriously sweet set of hourglass curves, especially in that crotchless body stocking.BTW, your sig is absolutely ***********. I can stare at it for ages.