Updating to Word 2003 on X5.0.2

After updating recently to Word 2003 (Office Suite), my
Printed Doc is now hosed (error messages about disabled macros,
images are gray boxes, all styles output as Sample Text at the
start of the output file, etc.).
I have build 801 (X5.0.2), but do I need to
uninstall/reinstall anyway? The RH Service Note 10492 dated May 28,
2003 only mentions uninstalling X5.0.1 then X5.
Leon

Well, I removed RH and Office 2003, installed Office 2003,
then installed RH; still getting the same errors (error messages
about disabled macros, images were "not updated" - meaning empty,
all styles output as Sample Text at the start of the output file,
etc.).
The MS message reads: "The macros in this project are
disabled. Please refer to the online help or documentation of the
host application to determine how to enable macros."
Please help.

Similar Messages

I recently updated my OS to OS X. I had to update my word and powerpoint etc... to 2011 version, but now when I want to open a .doc file made in word 2003 it removes all the text in it! I did not back anything up!

I recently updated my OS to OS X. I had to update my word and powerpoint etc... to 2011 version, but now when I want to open a .doc file made in word 2003 it removes all the text in it! I did not back anything up! All my mums work is on there for her job and now she cant use it! I need help fast!

If you updated from 2003 that must be on a Windows machine, can you recover them from there?

2003 Outlook after recent Microsoft update will not accept Word 2003 editor

Everything has been working fine for years and after the latest update from Microsoft, Outlook 2003 won't accept Word 2003 as my editor. I've attempted several of the "fixes" I've found on the web but to no avail. Any suggestions? My
wife's appears to be working fine with the exact same version of Word and Outlook. I even attempted to "repair" Outlook from my original disk but it still did not correct the problem. When I attempted to download Outlook from the Microsoft
web site it said I had the latest version and wouldn't allow me to download.
I feel this is a problem Microsoft created with their latest update. Surely I am not the only individual experiencing this issue. What has been done to correct this problem?

Everything has been working fine for years and after the latest update from Microsoft, Outlook 2003 won't accept Word 2003 as my editor. I've attempted several of the "fixes" I've found on the web but to no avail. Any suggestions? My
wife's appears to be working fine with the exact same version of Word and Outlook. I even attempted to "repair" Outlook from my original disk but it still did not correct the problem. When I attempted to download Outlook from the Microsoft
web site it said I had the latest version and wouldn't allow me to download.
I feel this is a problem Microsoft created with their latest update. Surely I am not the only individual experiencing this issue. What has been done to correct this problem?

Word 2003 crashes when converting to a PDF in Acrobat 9.3.1

OS                    :   Windows XP Pro SP3
Acrobat Version:   Acrobat Pro 9.3.1.
M.S. Product     : Word 2003
Not every file will crash Word 2003 when converting to a PDF using Acrobat Pro 9.3.1 but this particular file and some others will produce the following error:
%%[ ProductName: Distiller ]%%
%%[Page: 1]%%
%%[ Error: syntaxerror; OffendingCommand: ) '$ $ $ &$   ]%%
%%[ Flushing: rest of job (to end-of-file) will be ignored ]%%
%%[ Warning: PostScript error. No PDF file produced. ] %%
The co-worker was receiving the same error in Adobe Acrobat Pro 9.0 before we updated her to AAP 9.1.3.
I have read some other threads similar to mine but none of them answer the question well enough to try anything listed there. My co-worker can email me the Word file and I can print the file to my Adobe PDF printer just fine. I have Acrobat Pro 7.0.
Can anyone give me help on the cause and or solution to this problem????

Hi,
- syntaxerror indicates the file contains unintelligible PostScript code.
Any discussion of postscript errors, seem to consistently point to:
http://kb2.adobe.com/cps/328/328515.html
A troubleshooting guide is down in the bottom third of the page.
Be well...

Help file fails to generate RoboHelp 7 and Word 2003

Hello, I am back again with a new struggle. I am creating a WinHelp4 file for an older application using Word 2003 and Robohelp 7. There are several different results regardless of whether I make updates, corrections, add jumps, change Topic IDs or do nothing when I click on generate:
1. sometimes it generates and works perfectly, just not very often, usually between 8 and 805am ET.
2. sometime it will generate an error: Failed to compile
3. another error: filename.rtf does not exist, but it is there in the folder
4. generates a Warning, but I don't know what the warning is as it does not show it
5. generates a blank Help with only a single glossary definition
6. not enough memory ( 1 gb is available)
7. corrupted file, rerun and it works...sometimes
I have:
1. Started over
2. Rebooted
3. Uninstalled and reinstalled RoboHelp 7 and all updates
4. Tried adding one item (jump, new topic, changed topic, updates to TOC, renamed anything) at a time and then generated file
5. Create an html from Word...I know silly but it worked some of the time.
I feel like there must be a setting error I missing or something hidden that I need to remove. There is something or a very big bug! I can't find anything and RoboHelp 7, Word 2003 and creating Winhelp4 files have been fine the last 2 months...now...not so fine.
Please help! I am so close to finished!
Thanks,
and if this isn't enough, I cannot generate a print to PDF either, but used to!

I wish I could try on a different PC. This is a government facility and that is not an option. There are only 2 of us who have RH and I think the other person may have left last week...what luck!
As far as anything else running, that is possible....I may try disconnecting the network and see if it will work...that should check it, right?
Background resources are very probable as their are virus scanners and who knows what else...my rights are very limited, no Admin rights to the machine.
It just amazes me that it has worked and now at the very final stage and updates it will not. I am in early when it usually works, 745a ET and it failed. These are the error messages and I usually get this type:
Warning - HC4004: datcap.rtf is not an RTF (Rich Text Format) file.
Warning - HC4009: The Topic ID "Data_Capture_Operations" specified in the Project files as the Default Topic does not exist.
What is odd, is they are both there and have worked consistently up until this recent failure....cannot complile.
I know this is long, but here is the notpad error:
Starting compilation...
WinHelp preprocessor 7.01.002
Compiling C:\Documents and Settings\jkmalone1\My Documents\My RoboHelp Projects\CRS On Line Help Individual\DATCAP\!SSL!\WinHelp_4\DATCAP.hlp ...
Preparing to create WinHelp...
Clearing output folder...
Filtering out conditional text...
Processing DATCAP.rtf...
Processing DATCAP.rtf...
Removing watermarks...
Processing DATCAP.rtf...
Collecting Topics' Information...
Processing DATCAP.rtf...
Removing broken jumps...
Finished preparing in 4 sec(s)
Generating WinHelp system...Microsoft (R) Help Compiler
HCRTF 4.03.0002
Copyright (c) Microsoft Corp 1990 - 1995. All rights reserved.
Datcap.hpj
HC4004: Warning:
datcap.rtf is not an RTF (Rich Text Format) file.
HC4009: Warning:
The Topic ID "Data_Capture_Operations" specified in the Project files as the Default Topic does not exist.
3 Topics
0 Jumps
0 Keywords
0 Bitmaps
Created C:\DOCUME~1\jkmalone1\Local Settings\Temp\RHTemp12\Datcap.hlp, 13,205 bytes
Compile time: 0 minutes, 0 seconds
0 notes, 2 warnings
Finished compiling WinHelp in 6 sec(s)
Compilation complete.
WinHelp (WinHelp 4) was built successfully:
C:\Documents and Settings\jkmalone1\My Documents\My RoboHelp Proj
There has to be something causing this...it ran quickly this am but failed with the above Warning errors. The file is not successful although it built a sort of Help...one definition of one word....and nothing else.
Suggestions:
Thank you for taking an interest...this has me so puzzled.

Can't convert Word 2003 file to PDF

Downloaded the trial version of Adobe XI (Win7) and am using Word 2003. Tried to create a PDF from the Print menu (didn't work); the built-in menu in Word (didn't work). All I get is a 'PDF' file on my desktop (not saved as the name I initially gave the file) and, when opened, it's just a message stating the PDF file couldn't be created due to incombatibility w/Word.
HELP!

1) First i install Ms Office after then i install Acrobat 9.0 and update 9.2.0
2) that time also Word to pdf Conversion display same error
3) and 3 times i reinstall acrobat but not change .
4) this error my System only show, but same config for other system is not show
how can i solve, plz help me.
by,
Seenu

Missing text in list items when coverting an MS Word 2003 Document

When converting a document from MS Word (2003) to PDF, (using Acrobat 9 Pro.) text is missing from either an ordered or unordered list when the text is within a list item and spans across to a second page.
This symptom is present when using the following methods of creating a PDF.
·         In windows explorer, right click and convert to PDF
·         Using the Convert to PDF button in the MS Word 2003 tool bar
·         Using the Convert to PDF in the File Menu of MS Word 2003
The only workaround seems to be:
·         Click File
·         Click Print
·         Select PDF from the list
·         Print
I can't seem to find any updates or fixes either from MS or Adobe that addresses this issue. This issue is present on 5 computers, has anyone had this problem and found a solution o_0

With WORD 2003, set the printer to the Adobe PDF printer and then go back through the document to check for the layout and such. Then print (or use PDF Maker). The other option is to go into the WORD Options, way down in a list of compatibility settings, and turn off use printer metrics. I think either of these will solve your problem.

Adobe Acrobat 9 still can't convert Word 2003 files?

http://forums.adobe.com/thread/673769 is a link to the same discussion a year ago. There was no option for me to add a reply, so I had to create a new discussion here.
HAS THIS PROBLEM BEEN FIXED? Fujitsu's pdf printer S1500 comes with a full OEM version Adobe Acrobat 9 Standard, which I just installed. Immediately it caused problems with Word 2003, just as the above discussion link illustrates. Clearly that's a problem with Adobe Acrobat not being able to read SOME fonts. Where is there any bug fix for this?
Why would a customer want to upgrade Adobe Acrobat, if he can't get font support? In my case, it appears that GREEK FONTS are not supported, which makes no sense, if the fonts are installed in Windows. The pdf-converter knock-offs like Smart Creator PDF Pro can convert just fine -- so why not Adobe Acrobat? Who wants to pay more for Adobe, if it is worse?
So again I ask -- has this problem been fixed? Very unprofessional, if the answer is 'no'.
Very unproductive, too. I spent hours on computer crashes, reinstall uninstall detect and repair, just like the posters in that thread above, from a year ago. Businesses don't need this kind of aggravation. IS ADOBE EVEN LISTENING? Very unprofessional, if the answer is 'no'.

First, this is a user-to-user forum and not one for Adobe. They are sometimes around, but not on a regular basis. The lengthy discussion in the link did not apparently get folks to a solution. I did not see your handle in the discussion.
Two common errors were suggested, one the color setup and the other was font errors. Keep in mind that just because you have a font, it might not be able to be embedded in the file. That is due to copyright restrictions. The font file has to have the permission built into it to be used. That may be the case for any font that you download from another source. Most of the MS fonts are licensed for embedding.
Also, just because you have a font with the same name, does not mean it is the same. There are often multiple versions of the fonts, some that are useful and others not.
Out of the linked discussion, I have no idea what issues you are having -- there were many. I use AA9 with OFFICE 2007 and have no problems. I also use AA8 with OFFICE 2007. For AA7 I have a machine that runs OFFICE XP (2003). None of these have issues. To be able to help (if we can at all) it is necessary to track down the conditions when the problem occurs and possibly try to replicate it some. A few folks mentioned 64-bit systems in the linked discussion. The 64-bit systems have caused a lot of problems and generally require the updates for proper opertation.
From the point-of-view of trying to fix things without delving into the specfics, all I can suggest are a repair and then updates to the latest version of Acrobat. The updates should be able to be done from the Help menu, but if not from there you can download them from the Adobe Downloads>updates site.
Probably not considered much help at this point, but I really don't have enough information to home in on the problem. It may be that my copyright comment about fonts is really the issue (you should get an error message from Distiller if you print to the Adobe PDF printer that suggest the problem. As far as other packages, if they do indeed embed copyright fonts that do not have permission, then you are technically violating the law, even if allowed by the software. I have no idea if that is the case, but it is a possibility.

Word 2003 always asks to save the normal.dot since Acrobat 9 was installed

Hello,
Until Acrobat 9 Standard was installed on the 5000 PCs of our company, the following issue never occured.
As soon as Acrobat 9 Standard was installed, our users started to complain of messages asking them to save the normal.dot every time Word 2003 or Outlook 2003 if Word is used as editor, is closed. And even if they save the normal.dot, of course, next time they are requested to save again.
And if we uninstall Acrobat 9 Standard on the PCs concerned, the issue dissapear... and reappear if we re-install it.
So, the issue is clearly linked to Acrobat 9 Standard.
Of course, the Word 2003 option "Confirm to save the normal.dot" is NOT checked.
It doesn't seems to happens on all the PCs but we can't isolate the commun point between those which have the issue.
All our PCs are made by ghosting so are pretty similar, with Windows XP SP3 avec Office 2003 SP3... and now Acrobat 9.1.3 Standard.
In case that would help the diagnostic, on the PCs without the issue, the message doesn't appear, but, still, the behavior of the normal.dot changes : the time stamp changes every time Word or Outlook is closed. Before the install of Acrobat 9, the timestamp was not changing everything, but only of changes were made.
So, I guess Acrobat 9 Standard (probably the add-in for pdfmaker) forces the saving of all the .dot everytime Word or Outlook is closed.
Can you help us ?
Thanks

Thanks for your reply, but the issue is the same even when Word is not the default editor in Outlook.
Regarding the Office 2003 and Acrobat 9 updates, we are already up-to-date for Acrobat 9, but it's true that all our PCs have not yet received the SP3 for Office 2003, so it may be a trail to follow.
But I think the issue also happens even on some PCs with most up-to-date Office 2003, so I'd say it's probably not the solution.
But it doesn't seems that this kind of issue is widly encountered (I mean elsewhere than in our company).
So there is probably something specific to our environnement. And since we pretty much "lock-down" the PCs (to avoid users to mess with it), it's not impossible that some restrictions somewhere on the PC causes the issue... at least to some categories of users who are missing some authorisations.
But I'm sure that when we uninstall the "Adobe PDFMaker" component (in add/remove programs), the problem dissappear. So we are probably going to adopt this "solution" to make the steam goes down among our annoyed employees... until we'll find a better one.

PDFMaker for MS Word 2003 posts UnCheckout on UnSaved documents

Hi
We are getting a very strange unexpected bahavior with the PDFMaker plug-in for MS Word.
Use Case:
1. A user opens a MS Word document hosted in SharePoint.
2. Makes some changes to the document but does not hit the save button.
3. User uses Toolbar Icon or uses Adobe PDF=>Convert to Adobe PDF menu option to convert the document to PDF
The plugin sucessfully converts the document to PDF with the latest changes in it. But, somehow fires an Undo Checkout onto the document and all the changes in the document are lost. (And as an observation, this behavior is not observed with PPT files)
If steps 1-3 are performed on a .doc file present in local system drive; the plug-in pops-up a message saying
"Acrobat PDFMaker needs to save the file before continuing.
Do you want PDFMaker to save the file and continue?"
Now my question(s) is/are
1. Why plug-in didn't display any message for the document when edited from SharePoint?
2. Do we have any fix/updates to address the issue.
To help is diagnosis my environment details are
1. Windows XP SP3
2. MS Word 2003 SP3
3. SharePoint 2007
4. Adobe Acrobat 9 Standard
5. Could not figure out the version of PDFMaker plug-in
Ref: http://forums.adobe.com/thread/754639?tstart=0

Hi Michael
Thanks for your reply.
But, my question is why the PDFMaker plug-in does not display a "Save" message when the file is edited from SharePoint?

Acrobat Pro 9.2 crops text when converting from Word 2003

When converting a Word 2003 file to PDF, using either PDF Maker or directly from Pro 9, the converted file crops a few lines of text at the top of some pages. Converting the same file by just printing to PDF is a work around, but this method does not create bookmarks, so is not preferable.
I create an updated version of a particular file monthly, using the old file as a basis. The file will always have tracked changes in Word which are all accepted before converting the file, and the file always has a watermark, which is removed in Word and the file saved before converting to PDF.
Now here's the weird thing, if I remove the watermark in Word, save the file and convert to PDF, the cropping occurs. But if I leave the watermark in the saved file, convert to PDF and remove the watermark in Acrobat, no cropping occurs! This is an OK work around too but I'd rather not have to do the workaround at all.
I've tried all the variations and settings I can think of, but I still end up working around the problem every month.
Any ideas?

They won't show up unless
you have click on each text box
Go Format > Shape
click on lines
chose desired line color for the borders.
once the Borders a colored they will show up in the created PDFs.

Acrobat X Pro: Word 2003 Hangs Up When I Print to Adobe PDF

I have to print to Adobe PDF a LOT. Recently, I have been unable to do so from Word 2003. Whenever I go to print, it says "Word is preparing to background print your document" and freezes. I have experimented with turning background printing off, but that doesn't seemt o help. Help please!

You might also play with the printer spooling. Just change it to the opposite of what is currently set and see if that resolves the issue. You might also try to print to file with the Adobe PDF printer and then opening the file in Distiller to complete the process (the file will be a PS file, possibly with a PRN extension). If the latter works, you at least have a workaround for now.
You might also go to Help>Repair and see if that resolves the issue. I would also recommend the updates with Help>Updates.

J6480 not printing to word 2007 or word 2003!

Relatively new J6480 AIO will not print a word document from Word 2007 or 2003 version. All other forms of documents from the office suite can be printed i.e. Excel, power point, microsoft pub. etc. Even pdfs. Any suggestions?

Don't know if you can still update your WORD, but this sounds like a common WORD problem, though I have not heard about it with 97. I assume you get the same result if you print to paper, always a good check. If so, then start looking at WORD.

Character Direction override in Word 2003 imports

I've searched for Character Direction and seen mainly mentions of ME and foreign language conversions right to left and left to right. We do not use ME or any foreign language features. The behavior I'm troubleshooting for InDesign CS5 7.0.3 importing Word 2003 docs on a Windows XP macine, is as follows:
I have hundreds of Word 2003 documents, used in a production environment where editors update text daily or weekly, the production dept. imports into newsletters in InDesign. We go from import to finished product at the printer sometimes as quickly as 15 minutes.
In CS4, all of these documents import into my publications without overrides, using Microsoft Word Import options set for Customize Style Import, and style mapping used to map Word paragraph styles to ID paragraph styles
After the CS5 conversion, every one of my Word 2003 documents for all of my publications come in with overrides showing hyphenation settings and character direction that did not appear with CS4. This is despite my mapping styles, and the fact that these options can't even be (as far as I can tell) a paragraph or character override inside Word.
I went back to CS4 to make sure there were no changes in the Word docs. They worked perfectly, no overrides.
Inside Word 2003, I had to go to Tools > Language > Hyphenation and make the hyphenation setting in the Word doc match exactly the hyphenation settings for the paragraph style it was being mapped to in InDesign to make it go away at import.
Now I am left only with the character direction Left To Right override, which I can't figure out how to fix.
I can't find a way to set this in Word, and I can't find a way (since I don't have ME) to change it in InDesign. It is not practical for me to run a script for every import or continue to reset the overrides manually, because we simply don't have to the time, our deadlines are too tight and frequent. Plus, if we miss one, there are definite consequences, because the data is exported in a variety of formats for reuse automatically via scripts, and the override is messing up my exports.
I was hoping I'd see a post that says, "Ah yes, the Word filters in CS5 were updated, and now we look for hyphenation and character direction, and here's what you can do as a workaround" but I'm not seeing anything. If I can't define left to right in the regular version of ID or in Word 2003, does anyone have an idea how I can get my import to ignore it again?

I hate it when I know too much about MS Word.
I don't have Word accessible right now, but you can set character direction in (the Windows version of) Word. I don't remember the exact details off-hand. Character direction is not the only overrides I've seen make its way in. I've seen some CJK features get imported as overrides as well (by users not using CJK languages).
It actually depends on your OS and your version of Word, I think. In Word 2007 on Windows 7, you need to have a RTL keyboard installed in order to expose the right-to-left-paragraph and left-to-right-paragraph buttons on the ribbon. I think that Asian scripts are on in all installs of Word 2007, but since our OS has some Asian keyobards turned on by default by Group Policy, I'm unsure of this. In Word 2003 on Windows XP, you need the, oh heck I can't visualise the menu, something like "Enable complex script support for right-to-left languages" in the Region and Language tab in Control Panel.
For all recent versions of Word, you can check the Fonts window (control-D) to see if you have one, two, or three scripts enabled.
Font = Latin-script
Asian text font = CJK
Complex scripts = Thai/Lao/etc. and Arabic/Farsi/etc.
Finally: It's possible to have a RTL paragraph in a Word document on the machine of someone who does not have the Complex Scripts dropdown in the Font menu in Word. Likewise, it's possible to have paragraph styles in Word with CJK information on a machine that does not have CJK support turned on in Word (I have seen this numerous times in the Win XP/Office 2003 era).
So, in terms of the original post - I haven't yet figured out if this is a new feature of CS5, or something about one's install of Word or Windows, but there are so many variables that the only obvious solution to me is "a workflow in which overrides are always cleared." You don't like that solution, I understand, but any other solution would require some extended troubleshooting of the entire workflow, including all installs of Word that might contribute a Word doc to be placed in ID.

Word 2003 - Acrobat XI Std. - autotext normal.dot - unable to change

After installing Acrobat XI Standard at Word 2003 i can not Change the Autotext entries at normal.dot.
Before installing XI Acrobat 7 with the ppecial patch was installed, but since the last Windows 7 Update, Acrobat 7 did not run.
What can i do?
Thx

Hi, the installation of the Acrobat was completely normal. After installation, I could not make any more changes to the text blocks / autotext, that are stored in the files normal.dot. Word makes no changes to the file normal.dot when closing of Word. I uninstalled Acrobat again and the changes of the text blocks normal.dot are again possible. Something in Acrobat blocked the storage of text blocks.

Updating to Word 2003 on X5.0.2

Similar Messages

Maybe you are looking for