T
TLC
Does Office 2003 have the compatibly to open up Office 2007 documents? If so,
how is this done?
Thank you.
how is this done?
Thank you.
T
Tim
Natively, no. You need either the compatibility pack from Microsoft'sTLC said:
web site or you need to ask the person creating the 2007 document to
save it in 97-2003 format.
Tim
T
TLC
Thank you. Could you please send me the link for the compatibility pack?
Also, will this pack interfere with the 2003? If you open up the 2007 file
with the pack will it allow you to open in 2003 and save it as a 2003
document?
Also, will this pack interfere with the 2003? If you open up the 2007 file
with the pack will it allow you to open in 2003 and save it as a 2003
document?
B
Beth Melton
Here's a link to the Compatibility Pack:
http://www.microsoft.com/downloads/...70-3ae9-4aee-8f43-c6bb74cd1466&displaylang=en
The pack won't interfere with Office 2003, it simply enables you to open and
edit Office 2007 files and use them as you would any Office document.
Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Coauthor of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/books/9801.aspx#AboutTheBook
Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
http://www.microsoft.com/downloads/...70-3ae9-4aee-8f43-c6bb74cd1466&displaylang=en
The pack won't interfere with Office 2003, it simply enables you to open and
edit Office 2007 files and use them as you would any Office document.
Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Coauthor of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/books/9801.aspx#AboutTheBook
Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
F
funnybroad
This might help explain it better than most documentation provided by
Microsoft:
http://www.slideshare.net/funnybroad/office-2007-compatibility-mode-confusion
Microsoft:
http://www.slideshare.net/funnybroad/office-2007-compatibility-mode-confusion
B
Beth Melton
Unfortunately, I think the content on that page adds even more confusion to
a topic that should be fairly simple. I fully understand compatibility
between the Office apps and various versions and after reviewing the content
I felt confused. :-(
As an author, I've found if I don't fully grasp what I'm writing about then
I'm unable to properly convey information to others. Since the author did
note they are confused I suspect that's what adds to the confusion. Too bad,
really, I suspect it took a great amount of time to put it all together.
Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
a topic that should be fairly simple. I fully understand compatibility
between the Office apps and various versions and after reviewing the content
I felt confused. :-(
As an author, I've found if I don't fully grasp what I'm writing about then
I'm unable to properly convey information to others. Since the author did
note they are confused I suspect that's what adds to the confusion. Too bad,
really, I suspect it took a great amount of time to put it all together.
Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
F
funnybroad
The bulk of the content presents the actual inconsistent behavior and
inconsistent (and at times incorrect) documentation of the tools provided for
Office 2007 compatibility in many different scenarios.
The author did not create the inconsistent (and therefore confusing)
behavior. Microsoft did.
The author is not an "author" by profession, but an I.T. professional with
20 years of experience running very large-scale migration projects involving
operating systems and/or software systems such as Office.
The author would be very interested in finding out if/how the responder to
this post was able to get thousands of non-I.T. and non-author users in a
large company to:
1) Learn and understand this compatibility "topic that should be fairly
simple" and to "fully understand compatibility between the Office apps and
various versions"
2) Learn and understand the drastically new interface
3) Learn and understand the new security features and prompts
…. All with minimal training, minimal reliance on user support
organizations, minimal loss of work, and minimal drops in user productivity.
inconsistent (and at times incorrect) documentation of the tools provided for
Office 2007 compatibility in many different scenarios.
The author did not create the inconsistent (and therefore confusing)
behavior. Microsoft did.
The author is not an "author" by profession, but an I.T. professional with
20 years of experience running very large-scale migration projects involving
operating systems and/or software systems such as Office.
The author would be very interested in finding out if/how the responder to
this post was able to get thousands of non-I.T. and non-author users in a
large company to:
1) Learn and understand this compatibility "topic that should be fairly
simple" and to "fully understand compatibility between the Office apps and
various versions"
2) Learn and understand the drastically new interface
3) Learn and understand the new security features and prompts
…. All with minimal training, minimal reliance on user support
organizations, minimal loss of work, and minimal drops in user productivity.
B
Beth Melton
Based on what I reviewed (I'm a technical reviewer too. <grin>) it seems the
content is more about pointing out inconsistencies that were found than a
"How to" guide. I'll also note there were several things that weren't
correct,
much of it due to changes that have been made in Help since Office was
released
and it was complied using Offline Help instead of Online Help.
Online Help is the most up-to-date content. For example topics that were
noted as missing aren't, some of the terms noted as inconsistent were terms
used in the beta and were changed in the RTM version. And some of what was
considered as inconsistant are actually minor bugs in the application. Such
as the title bar isn't getting updated as it should in the application.
I will note there were some good points, such as Help should use consistant
Help titles throughout the applications. (I plan on passing this aspect
along as a request/wish - there should be consistant taxonomy for content
that is the similar across the applications.)
If were compiling this type of content then I would forgo attempting to
point out flaws, or what might be perceived as flaws, I have found in
teh documentation. Doing so only adds confusion. The key to clear
and concise material is to focus on what readers actually need to know.
Such as:
- Feature changes in Word, Excel, and PPT when working in Compatibility Mode
- What happens to object that are not compatible with previous versions when
saved in an earlier file format. (For example, SmartArt is converted to an
image)
- What happens to these objects when converted back to the new file format
(For example SmartArt is no longer an image)
- What steps can be taken to default to compatibility mode. (For example
there's a registry hack for Word - not sure if this is documented by MS)
- How to convert Office documents created in the previous versions to the
new file format.
- Address where the topic can be found in Help and for this topic, perhaps
point out any errors that might be in the content. (Also note that the
content is subject to change since MS can update the help pages.)
- Provide links to the Demos that are available on conversion and
compatibility
- Provide links to various Help topics in each application that might be
helpful, such as this topic:
http://office.microsoft.com/client/helppreview.aspx?AssetID=HA101172971033&ns=WINWORD&lcid=1033)
- Provide links to the Ribbon mapping guides and interactive guides for the
new UI
I'm sure there's more but those are the ones that come to mind right now.
Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Coauthor of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/books/9801.aspx#AboutTheBook
Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Coauthor of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/books/9801.aspx#AboutTheBook
Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
content is more about pointing out inconsistencies that were found than a
"How to" guide. I'll also note there were several things that weren't
correct,
much of it due to changes that have been made in Help since Office was
released
and it was complied using Offline Help instead of Online Help.
Online Help is the most up-to-date content. For example topics that were
noted as missing aren't, some of the terms noted as inconsistent were terms
used in the beta and were changed in the RTM version. And some of what was
considered as inconsistant are actually minor bugs in the application. Such
as the title bar isn't getting updated as it should in the application.
I will note there were some good points, such as Help should use consistant
Help titles throughout the applications. (I plan on passing this aspect
along as a request/wish - there should be consistant taxonomy for content
that is the similar across the applications.)
If were compiling this type of content then I would forgo attempting to
point out flaws, or what might be perceived as flaws, I have found in
teh documentation. Doing so only adds confusion. The key to clear
and concise material is to focus on what readers actually need to know.
Such as:
- Feature changes in Word, Excel, and PPT when working in Compatibility Mode
- What happens to object that are not compatible with previous versions when
saved in an earlier file format. (For example, SmartArt is converted to an
image)
- What happens to these objects when converted back to the new file format
(For example SmartArt is no longer an image)
- What steps can be taken to default to compatibility mode. (For example
there's a registry hack for Word - not sure if this is documented by MS)
- How to convert Office documents created in the previous versions to the
new file format.
- Address where the topic can be found in Help and for this topic, perhaps
point out any errors that might be in the content. (Also note that the
content is subject to change since MS can update the help pages.)
- Provide links to the Demos that are available on conversion and
compatibility
- Provide links to various Help topics in each application that might be
helpful, such as this topic:
http://office.microsoft.com/client/helppreview.aspx?AssetID=HA101172971033&ns=WINWORD&lcid=1033)
- Provide links to the Ribbon mapping guides and interactive guides for the
new UI
I'm sure there's more but those are the ones that come to mind right now.
Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Coauthor of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/books/9801.aspx#AboutTheBook
Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/
funnybroad said:
Please post all follow-up questions to the newsgroup. Requests for
assistance by email cannot be acknowledged.
~~~~~~~~~~~~~~~
Beth Melton
Microsoft Office MVP
Coauthor of Word 2007 Inside Out:
http://www.microsoft.com/MSPress/books/9801.aspx#AboutTheBook
Word FAQ: http://mvps.org/word
TechTrax eZine: http://mousetrax.com/techtrax/
MVP FAQ site: http://mvps.org/