Word 2007 complex autofill date feature

I need to write the date in a heading (within the text body) and I need Word 2007 to autofill the consecutive dates into the following
headings in the document.
Example: I want to be able to write "Monday, 2/ 02" and I want Word to autofill "Tuesday, 2/03" and "Wednesday, 2/04" in the following headings within the document.
Any tips?

You could do this with field coding or with a macro. To see how to do it with field coding, check out my Microsoft Word Date Calculation Tutorial, at:
http://windowssecrets.com/forums/showthread.php/154368-Microsoft-Word-Date-Calculation-Tutorial
or:
http://www.gmayor.com/downloads.htm#Third_party
In particular, look at the item titled 'Calculate a Date Sequence'. Do read the document's introductory material.
Note that the calculations don't automatically update - you'll need to force them to (e.g. via Ctrl-A, F9).
Cheers
Paul Edstein
[MS MVP - Word]

Similar Messages

Disable automatic insertion of date in Word 2007

Hi
We use Office 2007 Danish and I need to find the setting that disables the automatic correction/insertion of dates in Word 2007. If I want to write
24. february 2011 it automatically corrects it to 24. february 2011-03-17. I have looked everywhere, but can't find the setting that I have to disable?
Can anyone help?
/Lasse

THIS WORKED ! Thanks Stefan. Sadly I have no understanding of how and why it worked and I wish MS would make something like this much easier to turn on and, more importantly, turn it OFF.
Thank you very much, I miss the old ? Help at the top of the toolbar.
I'm glad you found my reply useful. :-)
Note that newer versions of Word make it easier to turn off AutoComplete suggestions. In Word 2010 and 2013, you'll find the option at File tab | Options | Advanced.
Stefan Blom, Microsoft Word MVP

Word 2007 and Excel Chart - Merging

I am in the process of creating a Benefit Statement in Word 2007 and using the mail merge features to import my data from Excel. The only issue I am having is trying to create a pie chart at the bottom of the statement.
Any assistance or advice would be appreciated.

Please re-post if this is still an issue or purchase a case and have a dedicated support engineer work with you directly:
http://store.businessobjects.com/store/bobjamer/DisplayProductByTypePage&parentCategoryID=&categoryID=11522300?resid=-Z5tUwoHAiwAAA8@NLgAAAAS&rests=1254701640551

Bug? Accessibility Tags Converting from Word 2007

This seems like a minor issue, but it's one that could create a lot of frustration for a disabled person using a screenreader to read tabular data in a PDF.
As you know, Acrobat plays nicely with Office apps allowing users to create tagged (structured), accessible PDF documents from MS Office files. I just created a simple docx file with a table (attached), and when I converted it to PDF, I noticed a difference in the tags it creates compared to conversion from Word XP. As you see in the Word file, the table is very basic, except that one of its column headers is split into two cells. This is actually a very common technique for presenting table data. In order to automatically tag the header rows as table header cells <TH> in the PDF, I set the first two rows to "Repeat Header Rows."
Converting from Word 2007 with the "Save as Adobe PDF," or any other method that uses the Acrobat plugin, creates a tag tree that is missing a <TH> tag. I found the problem when I was testing a file with JAWS screenreading software. Using the JAWS "current cell" command (Ctrl-Alt-Numpad 5) to announce the column headers. It reads the wrong header for the current cell due to the missing <TH>. So, in my example file, it announces $2 and $5 as 2010 amounts rather than 2009. That could be pretty confusing to a screen reading user, to say the least.
I then compared the result to the new Word 2007 "Save as PDF or XPS" feature. That feature tagged the file properly and the header columns match up.
Compare the attached "save-as-adobe-pdf.gif" to"save-as-pdf-xps.gif". Note the empty (but necessary) <TH> tag in the latter image.
Just as a sanity check I had a coworker with Word XP convert the file. Those tags were correct too. So, this must be a problem between Acrobat and Word 2007.
Anyone have other observations on this? I'm going to be leading some accessibility training and right now, it looks like using the Word 2007 conversion feature is the way to go.
I'm using Acrobat 9 Pro.
Thanks,
Joe

Hi Joe,
I sense your frustration. For any organization that has to or wants to engage in providing accessible online information
a serious logistics support issue raises its head. To do PDF, HTML, whatever the proper way (and it can be done)
requires more resources (training, knowledge, hardware, software, changes to work flows, perhaps some more staff).
The is no "work smarter with less & pump out more" in this venue.
Yes, it is helpful (and necessary) to "be one" with the S508 "paragraphs" - WCAG 1.0 - WCAG 20.
However, once anyone begins to provide PDFs that must be "accessible" the first, single most important reference is ISO 32000.
The Adobe PDF References that preceded PDF becoming an ISO Standard are useful; but, ISO 32000 is the standard.
In this documentation there is full discussion of what *must* be done to provide an accessible PDF.
Without a firm understanding of this content, other information tends to bring about a defused opacity of focus which can
contribute to major conceptual errors vis-a-vis accessible PDF.
Leonard Rosenthol's AUC blog entry provides a link to the ISO permitted Adobe version (free) of ISO 32000-1.
http://www.acrobatusers.com/blogs/leonardr/adobe-posts-free-iso-32000
Additional, useful information is found in these two documents:
(1) - PDF Accessibility API Reference (from the Acrobat SDK)
https://acrobat.com/#d=J7bWW4LvNoznh8fHCsfZDg
(2) - Reading PDF Files Through MSAA
https://acrobat.com/#d=uIOvkVTP74kag3bXFJLIeg
About JAWS - Yes, much used. However, not the exlusively used AT application.
If I use Windows Eyes, NVDA, a braille reader, or something else then what?
JAWS *does not* define "it is accessible"...
re: (1)
"Game away and if it ...."
   Consider "Stop before right on red".
   "Compliance" is Stop on Red - Turn Right
   "Intent" (aka usability) is Stop on Red - Look Good for on coming traffic that has the right of way - Yield - when clear, turn right.
But, at least we are not talking about "left on red" 8^)
re: (2)
Just an observation. A defective product that claims to be "whole" can get entities (individuals/businesses) into a sticky wicket.
Putting a high volume of defective products on one's selves only increases the probability that one gets 'busted'.
Quantity replacing Quality just is not a success precursor.
Case in point - Target and the national class action legal action that was taken against it with regards to "accessibility" of online information/services.
Resolved now - see NFB's web site.
re: (3)
Ah, but what would Judge Judy or Judge Marily say?
Efficiency does not preclude providing a "whole" product.
I doubt that there will ever be a seamless "one-click" between products of any of the dominant software houses.
They are intense competitors. That this is the case does not abrogate others from providing a "whole" product, no?
So, if the organization wants the "we do accessible PDF" label then it pays the freight - Adobe Pro, training, appropriate work flows, etc
that permit delivery of PDFs that meet the standards for what a well formed tagged output PDF is (accessible is a sub-set of this).
For PDF there is no other way.
If this cannot be done then there is always HTML as an acceptable method (to some it is the preferred and only "true" way).
However, HTML, done "right" for accessiblilty is just as demanding in its own way.
With each AT version / dot version release, JAWS - Windows Eyes - NVDA & others hone in closer on utilizing PDF ISO Standard 32000.
That means if you deploy "accessible" PDF you need to provide PDF that live to the ISO standard.
Keep in mind that S508's paragraphs began when, effectively, HTML was "it". In software terms that was geologic eons ago.
For contemporary AT to effectively parse PDF, the PDF must be a well formed Tagged PDF having a format/layout that reflects a logical hierarchy.
Creation of all this must start in the authoring environment with the content author.
The post-process PDF output then assures that the PDF elements (tags) are the correct type, have the requisite attributes, etc.
Without this, AT will not be able to provide the end-user effect utilization of the PDF.
So, for AT to properly 'work' the PDF, <TH> elements *must* have the Scope attribute's value defined, Row and Column Span values defined, etc.
Scope, Row Span, Column Span, Table IDs and Headings must be added as part of the post-processing of a PDF using Acrobat Professional.
An alternative is the Netcentric CommonLook plug-in for Acrobat Professional. What it does, Acrobat Pro can do; however, the CommonLook
provides a robust user interface. Downside: at some $1k per seat it is not 'cheap' and it has a *steep* learning curve (Sitka Pass?).
Two table related resources are at this AUC thread (in post 3 and 4). They may be of some usefulness.
http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=23178
When the "smelly stuff" gets feed into the maw of the fan it's prudent to not be directly down stream, eh.
Consider Target and the situation they put themselves in.
Consider submittal of accessible PDF to fedgov or stategov agencies.
They won't be in front of the fan if usability of the PDFs becomes an issue.
Rather, it will be those submitting. After all the agency did say "accessible".
Better to slow down and do it right or ramp up resource loading to support "schedule" than to stake oneself out as someones "feed" tomorrow, no?
In the final analysis, for PDF, HTML, or any 'format', Accessibility is the Usability + Compliance.
Does it take improvements in professional development/training, adequate hardware/software, *time*?
Yes. But, it all comes down to "where the rubber hits the road" - what tires are you on?
It can be done. I do it one small step at a time every day. Often, that's what it takes.
Deliverables are provided; but, with no mis-labeling and the incremental progress is identified, celebrated and the whole thing continues until
the "road" is completed properly.
Don't want wash outs, bridge collapse or what not tomorrow <g>.
(But then I'm a fan of "Holmes on Homes" which may go a long way towards understanding my point of view when it comes to accessible PDF.)
re: function(){Return ....
Good question.
My guess - either from the cut & paste I initially performed from the application I'd been using to assemble write up and screenshots or something associated with the Adobe Forum application.
It can't be that I'm 'special'; if that was the case one of my occassional lotto quick picks would have been a big $ winner long ago <G>.
fwiw -
You'll find a number of "Accessible PDF" related resources in the threads at the AUC Accessibility Forum.
http://www.acrobatusers.com/forums/aucbb/viewforum.php?id=18
Two Accessible PDF related on demand eSeminars are also available.
Look for Duff Johnson's and Charlie Pike's (on page 2) eSeminars.
http://www.acrobatusers.com/learning_center/eseminars_on_demand
Be well...

Tiny U's when converting from Word 2007 to Acrobat 9

When converting a MS Word document that has an underlined word in it, the PDF has very small capital U's before and after the underlining. This is when going from Word 2007 on Vista to Acrobat 9 (CS4). Anyone else experience this?

Here's how I can duplicate this.
1 - Open a new document or an existing document
2 - Underline any word using either the Ctrl-U keystroke or by use of the ribbon bar option (Word 2007). By the way, this occurs only in Word, works well in PowerPoint.
3 - Save document either as .docx or .doc
4 - Convert to PDF by selecting the Acrobat ribbon and clicking on Create PDF.
5 - View PDF, zoom to approximately 800% to see the very small capital U's
It should also be noted that if the "Enable Accessibility and Reflow with tagged Adobe PDF" is unchecked, this issue goes away. However, this is absolutely not a viable option because all of my documents must be accessible for persons with disabilities. Furthermore, in theory I should/could be able to create the PDF from Word without the tags and use Acrobat's "Add tags to document" feature, but Acrobat doesn't handle complex documents well, or as well as creating the tags directly from Word.
To see an example see this:
www.humtech.com/upload/test.doc
www.humtech.com/upload/test.pdf

Distiller 8.0 / Word 2007: Loss of Summation and Integral Signs in Equations

Software: MS Word 2007 and Acrobat 8.0 on Windows Vista. Issue: I have a huge word file with numerous complex equations produced by field codes (not the Word Equation Editor, which is too cumbersome for this task). Many of them feature integral and summation signs. When distilling the file, none of the integral and summation signs which are part of these equations show up. One relatively simple example: {EQ f(r) = \I\Su(h=-¥,¥, ah cos(2p hr) + bh sin(2p hr))}. The code \I\Su(,,) is supposed to produce a summation sign, and it shows up nicely in Word and when I print it with just about any printer, but distiller eats the S/Sigma (or the integral/ò) signs. It does convert any Sigma entered as plain Symbol Greek text, but not when produced by field codes.
According to http://www.math.clemson.edu/~bmoss/math_on_web/math2C.htm, this issue isn't new but has been around in older versions of Distiller/Word.
Question: is there a fix for this? (or if it has been addressed before in any forum and I missed it despite my searching for a long time, please indicate where I can find infos about this).
Thanks in advance (had it misfiled(?) in the forum Distiller Server Windows...)
GR

I now found a fix for the problem. The problem is that Distiller does not convert any "Symbol" font characters beyond code no. 220, which is where the summation and the integral sign are located. It is advisable to use other math fonts instead, like, e.g., the "Unicode Symbols" font (free dowload from http://users.teilar.gr/~g1951d/download.html), and to NOT use Word's equation editor function \i to create integrals or sums, as it relies on above Symbol font. Instead, use a nested overwrite function: \o(\o(∑, h=-¥),¥).

Word 2007: Error when saving file that contains equations

Using Microsoft Word 2007, version 12.0.6425.1000 with Service Pack 2
I am a High School Math teacher, and when working on a document that contains a number of math equations. When I try to save the document, Word refuses to save. It displays the following error: "A file error has occurred. <filename>. OK",
and I am unable to save the file.
Reading the forum, I have found this to be a very common issue going back to 2009, but I have not seen a definitive solution or patch.
I have found a workaround:
Creat a new document
Copy and paste from the corrupted doc each page, saving the new document after each page
Until I hit the error, then I know the page that has the issue, and can usually narrow it down to a specific math equation. Nothing fancy just some basic math.
Manually rewrite the equation in the new document and it will successfully save.
But the issue has been occurring more and more frequently now and it is becoming very frustrating. Any help would be greatly appreciated!

There has been a long time known issue with the equation editor. it causes document corruption by "losing" XML tags.
Apparently fixes for some causes of these problems have been rolled out in Windows updates. But the problem still exists. You've got it easy. A lot of people running into this problem are students working on documents, like a thesis, that is on a short
deadline ...
One identified cause of these problems is editing equations
after you created them. DON'T DO THAT!
If you have to change an existing equation, create a new correct one and delete the old one.
Simpler fix. Don't use Word (or Office) for creating equations. Find some other product, like a pencil.
Over in the "Answers" forum there are a couple volunteers, Tony Jollans and Jeeped
, who have been manually fixing this type of error if you post a new question or add a reply to one of the ongoing discussions on this issue.
Sorry.
If you want to invest the time to figure out what your error looks like you may be able to come up with a fix other than copy /paste method.
Can't open Word File because of end tag/start tag mismatch error... XML Tag
- XML Error – Fix It tool - “The name in the end tag of the element must match the element type in the start tag”
This error is caused when Word either “forgets” to write an XML tag, or writes them in the wrong order.
Tony Jolans was the first person that I heard of with home made tool to fix the problem. Now MS has released a Fix It for one specific variation of the problem.
If the tools don’t fix your problem, the file will have to be fixed manually, repairing the tag order.
The Fix It article notes that the document is still in a fragile state. You have to do some addition fixing to avoid repeats of the problem.
https://blogs.technet.com/b/wordonenotesupport/archive/2011/03/24/error-when-opening-a-word-2007-or-2010-document.aspx
http://support.microsoft.com/kb/2528942- FIX IT
This fix it will work for one specific tag error where there are equations and graphics in the same paragraph AND Office 2010 SP1 has not been applied.
Preventative suggestions
<snip Jeeped>
I don't think that anyone can completely stop editing equations, but pre-planning them should avoid unnecessary edits.
While I have no concrete, reproducible evidence that editing equations is a cause, I have made these empirical observations:
I cannot state precisely what many of the DOCX XML tags do, but basic XML syntax rules would suggest that code like:   <m:oMath><m:e><m:ctrlPr/></m:e></m:oMath>
... does nothing at all since it closes everything it opens and offers no content. It looks to me that this is a result of deleting one or more characters from an equation.
While Word 2010 reports these as a problem at: Line: 2 Column: 0 ... Word 2007 will still report the actual position, e.g.:
Line: 2 Column: 2726981 I keep a copy of Word 2007 side-by-side Word 2010 for no other purpose. It's the only Office 2007 program on my computer. This seems like it is actually a step backwards from a resolution since Word 2010 no longer seems
to be able to parse its own error.
Whether the syntax is truly useless and non-effective for any intent or purpose is actually beside the point. The syntax passes conformity tests and the DOCX
should launch. Why an 85 page document is 'broken' due to a few empty XML formatting tags while retaining legal syntax structure is beyond me.
I try to pass along the area that the problem was in and several times people have remarked that the area I report was the place they were last making modifications/deletions to equations (not additions) when the no-load corruption
occurred.
When no indication from the OP is offered on what was worked on last, the Line: 2 Column: 0 corruption often comes within a formula at the very end of the unfinished Word/Document.xml file and it may be inferred
that this was the last place being worked upon.
The corrupt DOCX files I've worked on are very commonly at the last stages of development with a large complex document. While there couldn't be a worse time for a corruption to appear, it would seem that small edits to existing content are causing
it and not large scale new content generation.
Not one of these points is a definitive 'smoking gun', but put together they seem to indicate
formula editing and not formula writing as a cause for the Line: 2 Column: 0 corruption. If it looks like a duck and quacks like a duck, it is most often a duck.
</snip>
Copy “True Autosave Macros for Office” to this place in reply
Let me fix it myself
If you are familiar with editing XML, you can try to fix the problem yourself by correcting the sequence of the mismatched oMath tags in the document. See the following example:
Incorrect tags:
<mc:AlternateContent>
<mc:Choice Requires=”wps”>
<m:oMath>
</mc:AlternateContent>
</m:oMath>
Correct tags:
<m:oMath>
<mc:AlternateContent>
<mc:Choice Requires=”wps”>
</mc:AlternateContent>
</m:oMath>
Note: You will have to use an application such as Notepad to edit the XML.
Manual Technique
<snip> A DOCX document is actually a .ZIP file that contains many internal components. There is an internal folder called word which will always contain a document.xml file. This file is the basis of the document's layout
and content.
Assuming that the DOCX archive structure has not been corrupted, it can be opened in an archive utility. I use
WinRAR for this. Once opened in
WinRAR, you can drill down into the
word folder and see the document.xml file. I use
Notepad++ as a text editing tool and have the .xml file extension associated with this program so i can simply double-click
document.xml in WinRAR to open an editing session.
Notepad++ has cursor positioning in the right-hand side of the status bar and finding the position of the error (supplied by a failed open in Word) is pretty straightforward. I look for empty formatting
tags first and only remove content if removing empty tags does not allow the document to be opened. I try to note existing content in the area that I make modifications in order that I can supply position reference information to the owner of the DOCX.
When editing, I assume the philosophy that kess is more. My target is to get the document to open in Word with as little modification as possible and let the original owner of the DOCX make any necessary adjustments.
I should mention that after making a change to word/document.xml you need to save it in
Notepad++ then go to
WinRAR and acknowledge that you want to update the file in the DOCX archive. Once the archive is updated, you can attempt to open the DOCX in Word to see if your efforts are successful.
WinRAR
Notepad++
</snip>
Further Fixes
The Fix it solution in this article should let you recover your Word document. However, the symptoms will reappear when you make any further edits to the document unless the core problem in the structure of the document is resolved.
To try to correct the core problem, follow one of these workarounds:
Install Office 2010 Service Pack 1
Office 2010 Service Pack 1 resolves this issue for new files. It will also prevent the problem from recurring with any files that were recovered with the Fix it solution in this article.
To download Office 2010 Service Pack 1, follow the steps provided in this Microsoft knowledge base article:
2460049 - Description of Office 2010 SP1
Grouping Objects
The steps provided work best under Word 2010:
After you open the recovered document, turn on the Selection pane. This can be found in the
Home tab of the ribbon. The editing group of the
Home tab has a dropdown button named Select.
Click the Select button, and then click
Selection Pane...
Press the Ctrl button on your keyboard and then click each text box in the selection pane.
Click the Group button under the Format tab. This will group all the objects together.
As soon as you have all objects grouped on each page, save the document under a new name.
Save the document in the .RTF file format
The steps provided work for both Word 2007 and Word 2010:
After you open the recovered document, click File and select
Save (for Word 2007 click the Office button and select
Save As)
In the Save As dialog box, click "Save as type:" dropdown and select
Rich Text format (*.rtf).
Click Save.
Click to view this
blog for more information about this issue.
Bonus tip: Win7 Win8 Math Equation Input Panel / Math input Panel
http://www.lytebyte.com/2009/07/24/guide-to-math-input-panel-in-windows-7/
http://www.7tutorials.com/windows-7s-tablet-input-panel-text-entry-and-handwriting-recognition
http://www.7tutorials.com/training-tablet-input-panel-work-even-better
http://www.7tutorials.com/do-math-easy-way-math-input-panel
Not an answer to the problem, just a bonus that may make it easier to input formula’s in Win7.
Here’s another one of those didn’t-know-it-existed-until-I-clicked-it-by-accident tools in Win7. It’s called the
Math Input Panel.
To access it, simply click Start, and in the Search Box that appears above, type in
Math Input Panel.
The Window should look like this:
Let the fine folks at Microsoft explain what it’s used for:
“Math Input Panel uses the math recognizer that’s built into Win7 to recognize handwritten math expressions. You can then insert the recognized math into a word-processing or computational program. “
Tony Jolan’s Automatic Fix
Download http://www.wordarticles.com/temp/Rebuilder.dotm Microsoft Office Word Macro-Enabled Template (.dotm) and open it.
Click Options button on the Security warning and select Enable this content.
Click the Broken Documents tab at the far right of the ribbon.
Click the Rebuild button in the left-hand side
Locate and open your corrupt document in the file open dialog.
That's it. The process will repair your document if possible and create a new document with (Rebuilt)
appended to the filename. Be patient as it may take a few minutes. If a repair is not possible, you can then post to a public file area and someone here can attempt a manual repair.
Manual Fix
XML Maker V1.1 is free. It will allow you to open the document.xml file and edit it. It also marks errors and warnings.
I just didn’t have much luck working with it.
A poster used XML Maker V2.1 (US$125, 30day free trial, enough for average person to fix a file)
Notepad ++ is a good, free editor for this type of task
Make a copy of the file
Rename the copy from DOCX to ZIP
Open … .ZIP/word/document.xml in notepad
Copy the contents of the file to clipboard
Open Word
Paste a copy of the copied XML into Word
(optional) the XML is one long string too hard to read, you can replace some tags, with that tag plus a para mark to break up the text to make it more people readable.
Open an XML validator, ie this site on the internet:
http://www.w3schools.com/xml/xml_validator.asp
Paste another copy of the XML into the “Syntax Check Your XML” input window
Click on “validate” button
Copy the missing tag, ie </mc:Fallback> (yours will be different)
Return to word Find: mc:Fallback> (without the </ so you find both open and closing tags).
Repeat find until you hit 2 open tags in a row. Then you just have to figure out where to put the closing tag between them.
Look for other tags before and after a proper closing tag so you can match the problem area to a good area.
Discussion by many affected people, a couple in discussions are also fixing problem if Tony’s fix doesn’t work
http://social.answers.microsoft.com/Forums/en-US/wordcreate/thread/581159d0-9ebc-4522-b30c-53e33e8268e1
Document Recovery
http://www.wordarticles.com/Shorts/Corruption/Formats.php
This page has the most readable description of Word file structures, DOC and DOCX, I have seen so far
The logical structure of a Word 97‑2003 format document is one of a series of elements arranged in a hierarchy, much like a mini file system. As an example, here is the structure of a simple Word 97‑2003 (.doc) format document:
MyDocument.doc
1Table
*CompObj
Word Document
*SummaryInformation
*DocumentSummaryInformation
The physical structure of the complete file bears little relation to the logical structure; it is, again, of a proprietary design, a compound, or structured storage, file. Briefly, and loosely, the separate logical elements of the file are broken up into
blocks; these blocks are treated as individual units, which units are then organised without regard for their logical arrangement, and catalogued, catalogue and organisation detail being held alongside the blocks themselves, to enable recombination into logical
components when necessary.
Just to give you a flavour, here are some views of three small parts of such a document, viewed in a hex editor:
Views of a Word 97-2003 format Document
The logical structure of a Word 2007 format document is one of a series of elements arranged in a hierarchy, much like a mini file system. As an example, here is the structure of a simple Word 2007 (.docx) format:
MyDocument.docx
_rels
rels
docProps
app.xml
core.xml
word
_rels
document.xml.rels
theme
theme1.xml
document.xml
settings.xml
fontTable.xml
webSettings.xml
styles.xml
[Content_Types].xml
As briefly as before, the [Content_Types] file and the _rels folders, along with the subordinate files therein, contain information about the logical structure, and the two files in the docProps folder contain much the same as the two Information files
in the old format. The document.xml element within the word folder holds the bulk of the document content and the other files within that same folder hold formatting details.
So, you might say, the internal structure of a document has changed a little, so what? There are, however, other changes that make a bigger difference. The first is that, although both logical formats are conceptually similar, they are wrapped up in
completely different ways to make a single file. Instead of the proprietary physical structure used for Word 97‑2003 format documents, a fairly standard, and open, Zip Archive format is used for Word 2007 format documents. The second change is that instead
of using obscure binary codes, everything in Word 2007 format documents, well almost everything, is held in XML format.
All data held as XML? In a standard Zip Package? It should be much easier to work with, then? Judge for yourself; here are some views of parts of a Word 2007 format document taken from a hex editor:
Views of a Word 2007 format Document
FreeFileViewer – reads 100+ text, Office, audio, video format file types – Can open some XML tag error files
http://www.freefileviewer.com/formats.html
Can't open Word file due to undeclared prefix, Location: Part: /word/document.xml, Line:91, Column: 49921
The most likely cause of your particular problem is that you are missing a
schema prefix reference within the opening <document ...> XML tag (usually the second one). Different
schema references are required for various types of specialty content. Here is a sample opening <document ...> tag with a large number of various schema prefix codes. If I remove one or two of these, i can reproduce
your error message.
<w:document xmlns:ve="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:r="http://schemas.openxmlformats.org/officeDocument/2006/relationships" xmlns:m="http://schemas.openxmlformats.org/officeDocument/2006/math"
xmlns:v="urn:schemas-microsoft-com:vml" xmlns:wp="http://schemas.openxmlformats.org/drawingml/2006/wordprocessingDrawing" xmlns:w10="urn:schemas-microsoft-com:office:word" xmlns:w="http://schemas.openxmlformats.org/wordprocessingml/2006/main" xmlns:wne="http://schemas.microsoft.com/office/word/2006/wordml">
It's impossible to blindly say exactly what you are missing but if you post an unadulterated copy of your document to a public file area (as noted above) and post the location back here, someone may be able to help. If you are going to go this route, send
a copy that has not already been subjected to repair attempts.
FWIW, while it may be hard to determine exactly which schema you may be missing, I do not believe that having extras causes any problems.
BTW, you don't actually have to rename the DOCX file extension if you have an archiving program. I use WinRAR and simply
<right-click>, Open With... to expose the archive.

Help me stop Word 2007 from crashing with PDFMaker!

I'm running Word 2007 (along with other Office 2007 applications) on a Windows 7, 64-bit computer that I recently migrated to. Every single time I try to create a pdf of a Word .doc or .docx file, the pdf is created OK but Word crashes. This is a huge nuisance, as I'd like to be able to keep other Word files open as I pdf the one I'm working on. I'm up-to-date with the Acrobat version (9.5.1); it's Acrobat Pro. Plenty of room on the hard drive (500 GB, of which 333 GB is free) and plenty of memory (8GB).
Note I'm able to create pdfs in PowerPoint and Excel without problems using the Acrobat add-in. I'm also able to create a pdf from a file shown in Windows Explorer by highlighting the file and using the right-click button to choose "Create PDF."
Any ideas?

I belive this is because technically Adobe is not supporting Windows 64 bit, so all the features we enjoyed in, say Windows XP, are not supported now. This is an ongoing battle with Adobe who apparently has 0 interest or intent in supporting 64 bit. They SAY they support it, but they only mean you can save to PDF. None of the features like hyperlinks, PDF Maker, TOC, shared reviews, etc. are supported. I think they are literally the only company not supporting 64 bit and their only workaround is to now use 64 bit. (Can you tell I am annoyed - I am. It's been over a year battling them and 0 action on their part.)

Adobe does not recognize footers in Microsoft Word 2007 to PDF

I have copied and pasted the details, below, from a previous message I have sent out to an assistive technology listserv.
I am encountering this problem with various builds and versions of Adobe Acrobat:
Acrobat X on a Windows Vista 64-bit build (note that this is the best Acrobat I can install on Windows Vista, Adobe Reader XI is not even supported)
Acrobat X on a Windows XP build, sorry, do not know the bit count (it is my work computer so I can't upgrade anything)
Acrobat 9 on a Windows 7 64-bit build.
I have also encountered and checked into whether or not the PDF reads (and does what I want it to) in JAWS 14, latest update (Feb 2013). We encounter the same problem with JAWS and this morning found out that there is a conversion error between Word and Adobe. (See this post, where the ---- are).
Summary, I have spoken with JAWS, put out a support ticket with NVDA via e-mail, spoken with Microsoft, and tried to communicate with Adobe about this issue for help and Adobe is refusing to help. The other places tried everything they knew but they could not get it to work. I even tried to strip all the page numbers from Word and number using Adobe's page numbering feature, but that was not successful either because I cannot use Roman numerals.
I would appreciate any feedback the Adobe Forums can give me; please note that I cannot post a sample document at this time as the only document I have is a private work document (cannot share those by policy, so I will have to make up a fake document if I get the time and energy).
Thank you very much for your time and expertise. The pertient info is above and below in "Original Message" and "Activities section" - the other information is there if you'd like to look. And to provide feedback to Adobe about things I think they could improve, since they will not let me email them directly.
----Original Message----
My question concerns the reading of Footers / Headers in Microsoft Word 2007 and Adobe Acrobat (headers/footers designed in Microsoft Word 2007 and then converted to PDF with "Bookmark" checked in Adobe Acrobat conversion settings).
The document is a word document containing 50+ pages. There are 12 pages of "front matter" that are marked with Roman numerals. Subsequently, the body text of the document has an Arabic number (1, 2, 3, 4, etc.) in the bottom right corner. Footers are used properly in the document. All Table of Contents links, which do link to both headings in the "front matter" and to headings in the body text, are picked up properly. Literately, the only thing not reading on the document are page numbers (the Word Status bar is reading its page numbers, but the page numbers in the footer are not reading).
I then need to convert the document to Adobe Acrobat PDF. Granted, I have a full copy of Adobe Acrobat X available to me, and my various assistive technologies have always functioned better when opened directly in Acrobat (rather than Adobe Reader). So, I set the accessibility options (from Word) properly, asking it to bookmark Headers and Footers as appropriate, thinking that this will pick up the page numbers and make them read as the bottom right corner of my PDF.
All links work in Adobe to navigate by section/heading. All figures are alt tagged. Everything is perfect - but the one thing that NVDA won't read are the page numbers. Visually, the page numbers are there on the document, but NVDA won't pick them up. Additionally, I also changed the appropriate page numbers in Adobe (Page Thumbnail Pane, on the Navigation Pane I believe it is called) - to reflect the section where it is Roman numerals and Arabic numerals. This did not help, and for what it is worth, I cannot get NVDA to voice when I am in this pane, so I don't seem to have a chance of getting the page number info from there.
NVDA reads the document just fine except for the above-mentioned snare. However, when it reads, it will go to the next page, and say, "Page 2 of 54, (page text), Page 3 of 54 (page text)," etc. when I will need it to say Page ii of 54 (page text), Page iii of 54 (page text)," and so on, changing to "Page 1" when the Arabic numbers are used.
I know that the Page Label issue is part of Adobe's issue, with them not releasing the PageLabel aspect. (I have looked through some NVDA tickets). I do not know how to put a "changeset" into my copy of NVDA though, or even if it would help (I have no computer scripting skill). The easy answer would be to upgrade to Adobe Reader XI and see if that helps, but I don't have the ability to put it on every computer I use, and *I need this file to read consistently across multiple versions of Adobe* (including Adobe Reader/Acrobat 9, X, and XI). (This file is also going out to people who may not have the latest version of Adobe, but are also running some copy of NVDA, either a portable or a full install).
Is there any way to pick up the Footers with page numbers voicing in NVDA, and/or have it read the user-editable page number box that is on Adobe's Toolbar (next to the 1 of 54 parentheses). This user-editable box, to jump to page numbers, reflects the Roman numerals I have loaded into the pages of Adobe. When I press Ctrl+Shift+N in Adobe, I can also go to the appropriate page (if I type in iii, it will take me to iii, if I type in 34, it will take me to the Arabic number 34 -- NOT the 34 of 54, which would land me on a different page. And I want to land on the page that has the Arabic 34, so that's functioning fine.
I just need the page numbers in the footer to voice, "Page iii," or "Page iv," or "Page 29," etc. If I could get NVDA to do that, I could say to viewers of this document, "If you are using NVDA, remember to Ctrl+Shift+N to get the GoTo Box, then type in the page number you want if you cannot follow a link or a bookmark." This document is *very* accessible in my opinion with lots of ways to navigate...the only aspect of navigation that isn't being picked up are those footer page numbers!
I do have my Document Formatting settings on the NVDA menu set to "Report Headers," but that does not seem to help in either Microsoft Word 2007 or Adobe Acrobat. I have even switched the page numbers from the footer to the header to see if that would help and it didn't.
----Activities I have done today----
I spent over an hour on the phone today with Freedom Scientific (makers of JAWS) trying to troubleshoot this. We discovered that Footers will not read very well in JAWS and Microsoft Word 2007 (only solution is to stop reading document text and read Virtual Viewer text briefly, then go back out to document text, then back into Virtual Viewer which is NOT an acceptable or accessible solution whatsoever -- too much work for someone trying to read the document) -- and then we also discovered that:
Upon conversion from Word 2007 to .txt file (.docx to .txt), there are no alt tags for the figures in the document, or page numbers.
Upon conversion from Word 2007 to Adobe Acrobat X then to .txt file, every insert of a page number and footer is replaced with the same alt numberpad numerical code: the one that generates female. ♀No wonder JAWS and NVDA are skipping this, neither understand how to communicate it.
On the advice of JAWS Technical Support I contacted Microsoft Accessibility Technical Support and spent an hour on the phone with them. They say that unless Adobe can find a solution, it appears that it is impossible for Microsoft products to read the footer if JAWS was unsuccessful doing what I wanted it to do. The document/footer in question includes about 12 pages of front matter (numbered in Roman numerals) and 44 pages of body text (numbered in Arabic numerals).
I kindly explained to the Microsoft Support Agent that I found this issue hard to believe, although I understood. Sighted folks have the ability to make their documents look quite professional and that is the caliber and quality of documents anticipated from everyone, especially college students graduating from school, or job applicants. That a coding issue prevents the footer from being read properly, except in Edit view, is disappointing. The representative was with me 100% of the way. She completely understood where I came from. And yes, when I am designing the document myself, I know what I put there (or I pretty much do, anyway). But if I recieve a document, it is much harder to tell what is really there or not, or how the page numbers really lay. And this is confusing as heck, believe me.
I then called Adobe Technical Support, after having a brief online chat with them. Granted, I had to leave the chat in the middle because I got interuptted by something that was high-priority, but the woman chatting from Adobe says that chat is only for installation issues, and I will have to pay to open a support ticket. Excuse me? I have paid a hefty sum of money for Adobe Acrobat 9 and Adobe Acrobat X (work paid for the other Acrobat X copy). I deserve this problem to be troubleshooted for free. There was even a statement on the Adobe Acrobat X website that said Acrobat X users didn't have to pay for support, but Reader users did.
----Slight bit of rant and constructive criticism----
In speaking with Adobe Technical Support, I had to wait on hold for 30 minutes before my call was answered, and then I had to consent to being on hold countless times and had to answer, "Yes, I am converting from Word 2007 to PDF using Adobe Acrobat X" at least 6 times. The representative would put me on hold, then ask me the question, then put me on hold again, repeated 6 times over 45 minutes. At the end of 45 minutes (1 hour and 20 minutes of wasted time by now, that I must justify to my employer) - I told the representative I wanted to speak with his supervisor immediately, I did not care if he was trying to fill out a support ticket (and putting me on hold at least 4 more times in 10 minutes while he claimed he was filling out the support ticket) - and finally he put me on hold again and gave me to a very helpful supervisor. Within 6 minutes of speaking with the supervisor the supervisor had my support ticket filled out and I should recieve a call from Adobe within the next 30 minutes if his estimation was right (he estimated two hours, but it's been an hour and a half).
I have yet to know what can be done about my document. Freedom Scientific Technical Support is closed now for the day and I need to work tomorrow and Friday away from the phone. As I stated to Microsoft Accessibility Support, I truly feel that Adobe should read the page footers, every document says that Adobe should be able to read the page footers, and I feel slighted that as a person who uses assistive technology, there is some glitch that isn't making this happen. I am not blaming a specific place per se, except I am a little frustrated with Adobe especially since they have not gotten back to me, and I am frustrated with their customer service. JAWS customer service and Microsoft customer service were both exemparly, and I cannot say enough good things about them. My wasted time with Adobe however, that was disrespect in my opinion. And I certainly will not pay to open a support ticket, and my workplace has a site license. They've paid enough already.
If you've read this far, thank you. I look forward to replies, or at least understanding. And if anyone has ideas, I'd appreciate it very much (yes, I have tried taking the page numbers off and using Adobe's page number feature, but that would not allow Roman numerals. Only Arabic.).

Greetings NoNameGiven,
If I understand the problem correctly (I’m not sure I do) you would prefer ‘iii’ to be read as “eye eye eye” rather than “three”? The alt text property is the only way that I know of to make this happen. Hope this helps.
a ‘C’ student

Corrupted .docx file. Word 2007. Can't open the document. Tags mismatch. Help?

The Office Open XML file *.docx cannot be opened because there are problems with the contents.
Details: The name at the end tag of the element must match the element type in the start tag.
Location: Part: /word/document.xml, Line: 2, Column: 3487212
Hmm, I guess I should give some background info and what I've tried so far, right?
The document is in word 2007, Windows 7. Last night, I was in a hurry, and got a lot of things open. I was opening the document to do a few quick spontaneous revisions, but it was so laggy and I was late for an appointment, so I was feeling panicky
and frustrated. In hindsight, it probably wasn't the best option to just force shut the PC down cause word stopped responding in the middle of opening the document. Still, while I'm no Sherlock, I knew stopping it while it's in the middle of saving the document
would bebad, I didn't think stopping it while opening the document (and not really modifying the document at all, at least that was what I thought before), could have drastic consequences! The document's quite
large, a few hundred words, and about 500 or so pages. It's this really big project I was doing at work, for months now really, and because it's somewhat business confidential in nature, I can't exactly share it freely, or I would've uploaded a copy, sorry.
Anyway, I woke up this morning and opened it, and the error came up. By the way, the document was saved in a 2TB external hard with a few disk errors in the past, if that helps, even if I'm pretty much sure its not a problem with the hard. The error
came up... and yeah. I first made a copy, which I've been trying everything on, in case I do end up making things worse. I have no previous versions of it, just a relatively very old backup. Anything less than 80% recovery would set me back weeks with a wage
cut. The good news is that I was able to open the document in WordPad, managing to recover the first 287 pages (131,543 words), with no errors or data loss, and saved it in a separate file. Apparently, according to information I obtained later, MSWord tends
to not open at all when it encounters an error, but Wordpad tends to stop reading the rest of the code once it encounters an error. So, naturally, I assumed (so correct me if I'm wrong), that behind a few sentences I might lose due to the error, the rest could
also be salvageable. I then looked up the problem all over the internet. Read a microsoft article on troubleshooting/recovering corrupted documents (Open & Repair, Draft Mode, Creating Link, Recover text from any file converter, etc). No dice.
I first saw a similar question on answers.microsoft, and tried to use Tony Jollan's Rebuilder, macros enabled and all. Sadly, no luck.
I managed to make my first breakthrough when I found out that .docx was just a .zip file, and could be renamed as such, with the document.xml extracted and manually fixed using an XML editor (not that I knew how to do that, but I was desperate and
willing to learn). So, made another copy, changed extensions, and tried to specifically extract the document.xml. I believe that it is the main body text, right? That is the only thing really necessary for me, since everything I've done so far is entirely
spartan, with no fancy fonts, formatting, header/footer/notes, media objects, formulas, tables, bullet points, numbered lists, etc. All pure sans-serif text, with some Japanese Kanji thrown in. 500 pages of pure text.
I then hit a snag, when WinRAR encountered an error on extracting document.xml, stating that "CRC failed in word\document.xml. The file is corrupt". So I tried to fix this using several ZIP repair programs and stuff. Nothing worked. At
least not so far. Managed to extract an incomplete version of document.xml using WinRAR's 'Keep Broken Files' option when extracting. The extracted
document.xml came up to 3.31 MB while the original in archive is 7.53 MB. Viewed it in the Windows XML Editor which opened up the text in Internet Explorer, a jumble of text with no line breaks or paragraphs. Still, it actually extracted a few pages less than
the open-using-Wordpad method tried earlier. So trying to fix the archive again...
So I decided to give up the manual route for the meantime and focus on readymade solutions. I came across yet another microsoft article, but this one was at least more relevant than the last. It had this auto FixMe thing. I ran it, didn't
work. Apparently, as I found out later, "This fix will work for one specific tag error where there are equations and graphics in the same paragraph AND Office 2010 SP1 has not been applied."
Tried several (read: dozens) corrupt Word recovery software, from freeware to pro trials, to varying degrees of effect, although unsuccessful
in goal. Some failed to read it, saying it was too corrupted for them to handle, the best managed to recover about three-pages-worth less data compared to the Wordpad method. So yeah, anybody with a similar problem, always open it with wordpad first and recover
what you can. That doesn't mean I'm giving up though.
So here I am, tearing my hair out in frustration. Whew, I feel like I told you guys my life story. I guess worst case scenario, I report this to my boss, so I personally or from the company, I/we'll hire a team of professionals to deal with it.
But that's not an ideal scenario. It's gonna be out of my salary either way (the company has a firm policy of 'You reap what you sow'), along with a wage cut for making such an amateurish mistake even with continuous reminders to back it up every two sentences,
so I'd rather avoid that.
I'm currently looking to see whether there's a way to recover a previous version of an overwritten document somehow using a third-party software or something. (I didn't have Windows Backup enabled, so no previous version on Windows). So far, no
autosaved documents on MSWord AutoRecover, even though I have it enabled set to every 3 mins (or maybe I'm just not seeing it since I'm trying to look for it manually?). Or are the temporary files wiped on shutdown? I don't have 'Always save backup copy' option
enabled on word either.
So yeah, an auto fix, or a lengthy answer detailing what exactly I should do (from the very very basics), or a link to a site with such info, would be much appreciated. Seriously :D
Please. Thanks for at least making an effort :)

When a Word document file is corrupted, then you can try several methods to recover it:
1. First of all, you can try the recovery function integrated with Microsoft Word, as follows:
1) On the File menu, click Open.
2) In the Look in list, click the drive, folder, or Internet location that contains the file that you want to open.
3) In the folder list, locate and open the folder that contains the file.
4) Select the file that you want to recover.
5) Click the arrow next to the Open button, and then click Open and Repair.
You may find more information about this at:
http://office.microsoft.com/en-us/word-help/recover-the-text-from-a-damaged-document-HP005189610.aspx (for Word 2003)
http://support.microsoft.com/kb/893672/en-us (for Word 2007/2010/2013)
2. If you have multiple corrupt Word documents, then you can use the VBA macro provided in article
http://support.microsoft.com/kb/893672/en-us so that all the files will be opened in "Open and Repair" option automatically.
3. There are also free tools from third-parties that can open and read Microsoft Word documents, for example,
3.1 OpenOffice at http://www.openoffice.org. This is a very famous open source project that is designed to support Office file formats, including Word documents. The software can run under Windows.
3.2 LibreOffice at http://www.LibreOffice.org. Another free office suite.
3.3 AbiWord at http://www.abisource.com. This is a cross-platform tool that works under Unix and Windows.
3.4 Google Drive at https://drive.google.com/ also support to load Word document files.
Sometimes when Word fails to open your document, these tools may be able to open it successfully. If that is the case, then after the document is opened, you can just save it as a new document which will be error-free.
4. For docx files, they are actually a group of files compressed in Zip file format. Therefore, sometimes, if the corruption is only caused by the Zip file, then you can use Zip repair tools such as WinRAR at
http://www.rarlab.com to repair the file, as follows:
4.1 Assuming the corrupt document is a.docx, then you need to rename it to a.zip
4.2 Start WinRAR, go to "Tools > Repair Archive" to repair a.zip and generated a fixed file a_fixed.zip.
4.3 Rename a_fixed.zip back to a_fixed.doc
4.4 Using Word to open a_fixed.doc.
There may still be some warnings when opening the fixed file in Word, just let ignore it and Word will try to open and repair the fixed file. If the file can be opened successfully, then you can just save the contents into another error-free file.
5. If all above methods does not work, then you may try third-party tools such as DataNumen Word Repair at
http://www.datanumen.com/word-repair/
I have used it to repair some word documents successfully. It provides a free demo version so that you can try to see if the data you want can be recovered or not.
Good luck!

Error while previewing in Word 2007

I am using word 2007 and have xml publisher template builder for word version 5.6 build 45 in stalled on my system. I have installed MS .NET 2.0 patch also.
When i select for preview after loading the data, every time i hit the same error. the error does not chnage with the type of preview type chosen.
the error is
Windows cannot find 'C:\PROGRA~1\Oracle\XML'.Make sure you typed the name correctly, and then try again. To search for a file, click the start button and then click Search
Can anybody please help.

Now i have upgraded to Oracle BI Publisher Template Builder for Word 10.1.3.3.2 build 115
but still when i preview i am hitting error
Windows cannot find 'C:\DOCUME~1\user123\Local'. Make sure you typed the name correctly, and then try again. To search for a file, click the Start button, and then click Search.

Duplex Printing Problem - Word 2007, Vista and HP Officejet Pro L7780

I'm having trouble with duplex printing on my new HP Officejet Pro L7780, from Word 2007, running on a brand new Vista system. I've also had this same problem (repeatable) with two other computers, running XP Professional/Word 2003, XP Home/Word 2003. All of the service packs have been installed for the operating system, word, and printer.
If you print a landscape document, using the auto duplex setting for the HP printer, the margins will print out offset by .25 inches, on the left and rigt margins. So if your margin is 1 inches on right and left, the margins will print to .75 on one side and 1.25 on the other. This would be annoying, except that I'm trying to print brochures and books, which requires that the pages print out exactly as set up... "close enough" isn't working for me
The way I have replicated this problem is as follows: set up a document in landscape format, using the default margins. Insert an image on page one, size it so it takes the full margin area. On the second page, fill it up with text. Print the document, selecting the printer properties and setting Print on Both Sides=Automatic. The easiest way see the problem is by holding the document up to the light. The front and back margins should match and they don't.
Any help you can provide would be very much appreciated.
Diana

Diana,
This problem is perhaps much larger than you might have imagined. We have tried to work with Hewlett Packard for over two years on the duplex printing problems. In the process, we have expended over 100 hours of effort in troubleshooting the problem which has included updating software, reinstalling software, developing test documents, escalating issues, submitting technical findings, and in purchasing replacements. Unfortunately, our efforts to interact with Hewlett Packard excalated support have resulted in an aire of apathy, disinterest, incompetence, frustration, redundancy, occasional discourtesy, and an outright lack of professional decorum - something inconceivable of a large, reputable company.
We have identified several problems with duplex printing. The duplex printing problems include irregular margin increases (.25 to .50 inch), margin shifts, cut-off text, compressed text, and compressed graphics. Please note that most of these problems are only evident when printing documents from computer applications to the printer. If the user simply uses the front printer panel to copy in duplex mode, these problems are not always evident. This suggests that the printer mechanics are capable of properly duplexing and that the problem lies in the drivers.
The problem is evident on the HP OfficeJet Pro L7780, Photosmart L7180, Photosmart C6150, Photosmart 3310, and likely on many, many other HP models. The problem is evident on many computers (HP, IBM, Toshiba, and Dell), is evident in multiple applicatons (Word, Wordperfect, Excel, Peachtree, Notepad, and many more), and is evident on multiple operating systems (Windows XP Home, Windows XP Professional, Windows XP Media Center Edition, and Microsoft Vista).
We consider ourselves to be extremely polite, patient individuals, but have nearly been driven to outrage by the indignant disregard offered us by HP's escalation support department; a department which should represent the cream-of-the-crop in both service and technical expertise. Given the ease with which the problem can be duplicated, we expected an extremely quick resolution by HP who, to our knowledge, has never even made the effort to duplicate the problem in-house on our behalf.
Ironically, HP highly advertises their J.D. Powers rated technical support, yet it appears that they actually have extremely poor published consumer rankings in some of today's mainstream computer magazines. HP technical support makes no apologies for the fact the user cannot use a major feature of their printers, offers no indication that the problem is even being addressed, and off-loads the responsibility by suggesting that we contact Microsoft (who is to blame for this issue).
Thank you, Diane, for your message. We had a hard time imagining that we were the only one experiencing this problem, especially when HP promotes such a representation. Which also begs the question why HP plays like the problem does not even exist? I also fail to understand why HP technical support shows so little interest in a problem that is easily duplicated and adversely affects a major feature of the printer which is commonly used by individuals purchasing equipment for its duplex capabilities.
This is sad because we have been a loyal customer of HP for over twenty-five years. There was a time when we would have happily endorsed HP's steller products and steller support (provided you could get a problem escalated). Now, however, they all-too-often appear to offer equipment that fails to support advertised features which is backed up by sub-standard support and extremely expensive ink. This is an especially sad commentary for users who are buying HP's upper-end printers and computers.
We desire to know if there are others out there experiencing similar problems? If you have experienced these problems or would like samples of the problems we have duplicated, please respond. I think the more information we gather, the better our chance of a successful resolution to a serious problem.
Thanks Everyone!

Acrobat 9 Pro - Will it print to pdf with embedded pdf's from Word 2007?

Hello All,
We're considering upgrading to Acrobat 9 Pro or Extended. One of our concerns is whether it will handle the following:
1. We create very large documents and we like the ability to use OLE of existing PDF documents imbedded into Word 2007 which causes a new PDF window to open up from the imbedded PDF. It also displays nicely as an icon or the cover page within Word.
2. The challenge is when printing (distilling) that master document with any imbedded PDFs, the icon or cover page is displayed, but the OLE feature goes away and does not recognize the imbedded PDF any longer; Acrobat simply treats the imbedded PDF in Word as any other page in the distilling process.
3. We're not wild about bookmarking or linking to another PDF.
Does Acrobat 9 Pro or Extended resolve this issue?

The options availible for scripted print settings are all shown in the entry for "PrintParams" object in the Acrobat JavaScript Reference. Have you looked to see if these options fit your needs? If they do, and if the script can detect which PDF requires which options, then you're in business. But if the options you need are not there, then your only option is to set the batch process to display the print dialog for every PDF.
Thom Parker
The source for PDF Scripting Info
pdfscripting.com
The Acrobat JavaScript Reference, Use it Early and Often
http://www.adobe.com/devnet/acrobat/javascript.html
Then most important JavaScript Development tool in Acrobat
The Console Window (Video tutorial)
The Console Window(article)

Word 2007 "Save as Adobe PDF" - Pictures not showing up in PDF

Good Afternoon,
I have run into this error recently when using the "Save as Adobe PDF" to publish Word 2007 report.
Each report has an table - pasted from Excel 2007 "as a picture - when printed". The reports have a ton of other jpg pictures.
After creation, when I open the PDF, some of the tables appear to have become transparent. Where the picture used to be is a selection box, as if there were a picture there, but it's merely blank. All of the photos, frames, and Word-based tables show up. Some of the pasted-from-Excel tables also show up, not these ones.
Is there a reason for this discrepency? Is there a way to resolve the issue? I used the search bar and found nothing that matched my issue. All of my software is up to date.
Thank you for whatever help you can provide.
J

did you ever solve this issue? I have the same problem and "view large images" is the only answer I can find and it DOES NOT WORK.
I posted the question elsewhere, but nobody has replied. here's my situation:
When creating PDF documents from any software (Illustrator, Corel, InDesign, etc), color objects over 50% of the page size have white fill. If object has an outline, the outline will appear normally, but the fill will be white. I've searched forums everywhere and have found no answer. Most forum topics on this are issue focus on settings in the program that exported the PDF. I am 100% sure this is not an export problem, but is something in Acrobat itself (a missed setting? Corrupt program file?)
To provide the best information, I've done a little scientific research. Here is what I know:
Currently running Acrobat Pro 9.5.5
This is only happening on ONE install of Acrobat 9. Documents display correctly in Reader X and in Acrobat 9 on other machines.
Started happening a few weeks ago, I have no idea what changed.
"Show Large Images" in preferences dialog is checked. Unchecking it and rechecking it does nothing.
Have installed all available updates to the software
I experimented with different object sizes. At 50% of page size, objects appeared normal, at 51% filled object disappears.
Does not affect photos, only affects vector objects.
running this on Windows Vista 64 Bit

Acrobat Pro 9 - Conversion Error from Word 2007

I do not want to hijack the thread or question raised by another poster a short time ago but I cannot figure out how to correct the below.
Office 2007 fully updated
Vista 32-bit
Acrobat Pro 9.3.4
I have to provide data for someone else to assemble and publish and have been attempting to convert some Word documents nearly full of tables to press quality .pdf. Whenever I try the conversion, Acrobat Pro seems to re-center the tables both horizontally and vertically forcing the misalignment of the rows of data although any repeating headers remain properly placed. I can even see the table shift downward slightly when using the Acrobat conversion macro within Word. It may be adjusting the margins instead of re-centering.
I have tried using the macro within Word 2007, Create PDF within Acrobat Pro and Print to PDF as well as tweaking some of the settings such as lowering resolution and turned off unused settings such as enable fast web view, etc. The glitch also occurs with High Quality Print. Standard used to work but after the update to 9.3.4 that conversion shows the same problem. I even tried saving in Word 97-2003 format with the same results.
The documents in question do have custom page sizes and margins but do not use any abnormal fonts. I have tried changing the margins but the conversion to .pdf still changes the information and/or magins as described above. Row height seems to be correctly maintained.
I realize that a knowledgeable user can export the .pdf back into Word or other program but am trying to make it more difficult for someone to edit information which has always had extremely negative consequences in terms of data organization, layout and even integrity.
There has to be something really silly that I am overlooking.
Thank You

Thanks Bill.
Sorry for the delay, Verizon dumped its DSL +service to Frontier so we had one of the bi-weekly extended outages.
No changes occurred when I changed the default printer to Adobe PDF. All of my printers are new enough so that they can handle the current margins so I do not think that they is a problem there but changing the default as suggested by you and Michael eliminates that as the source.
I had previously been able to convert using the built-in converter in Word but was unsure whether or not the result would be press quality and was unable to find this information in my searches. I retested this and conversion using Word’s built-in converter works without a problem.
The conversion using Combine Miles > Merge Into A Single PDF also works without a problem with the highest quality setting. It took several hours to run but I guess or assume that it was because of the number of tags as this is a quick setting and therefore I could not disable the tagging which is not needed in this case.
I was also able to convert the same file which had been saved from Word 2007 into the 1997-2003 format as described above but the same problem came up when using the Acrobat macro and Create PDF from File. I had even created a modified press quality settings to modify settings like disabling autorotate, Object Level Compression, changed the binding option, lowered resolution, bumping the format up to PDF 1.7, etc., but all produce the same result. I have tried changing the document margins in case the conversion process rounded these but all produce the same artifact/problem except when I use Combine Files or the converter built into Word.

Word 2007 complex autofill date feature

Similar Messages

Maybe you are looking for