#1
|
|||
|
|||
Remove Compatibility Mode on DOCX files (batch)
How can I remove Compatibility Mode on DOCX files in Office 2013 x64?
I know 2 options: - Convert command - SaveAs command The problem is that I have 40 000 DOCX files. 90% of them with Compatibility Mode. Thank you. |
#2
|
|||
|
|||
See Graham Mayor's batch file handling Add-Ins. The second one (process 4) may do what you need. Otherwise, you will probably have to create your own macro to be called by the Add-In.
If it does help, I would urge you to make a donation to Graham for all of the time he will have saved you. |
#3
|
|||
|
|||
I found that these add-ins are not working well with Office 2013 x64.
I'll wait for the updated versions. Thank you |
#4
|
|||
|
|||
Quote:
I would recommend trying it (with copies) and see what happens. |
#5
|
|||
|
|||
I tried on 2013 x64:
- Batch Process Documents with Include sub-folders = doesn't working; - Convert Documents to DOCX = doesn't working, I receive an error. |
#6
|
||||
|
||||
IIRC, Graham's converter is for converting .doc-format files to docx/m-format, not for removing compatibility mode from docx/m-format files. What is your issue with compatibility mode, anyway? What that means is that the documents are backwards-compatible with previous Word versions. Do you really need to change that for 40000 docx files (and mess up their system date/time stamps in the process)?
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#7
|
|||
|
|||
1. I want to save to the latest format (with no Compatibility Mode) because Microsoft stated that:
"You can work in Compatibility Mode or you can convert your document to the Word 2013 file format." "Converting your document lets you access the new and enhanced features in Word 2013." 2. I found a way to remove Compatibility Mode from docx files using Graham's converter. 3. I found a way to preserve date/time stamps in the process. So, the main problem is using Graham's converter with 2013 x64. |
#8
|
|||
|
|||
I gave you links to two converters with a suggestion that you use the second one, not the "converter" but the batch process with process 4. Is that the one giving you the problem?
|
#9
|
||||
|
||||
Quote:
__________________
Cheers, Paul Edstein [Fmr MS MVP - Word] |
#10
|
|||
|
|||
Quote:
Run-time error '5825': Object has been deleted. |
#11
|
||||
|
||||
The process was not intended for the 64 bit version of Office, which I don't have access to and thus cannot test those functions which are likely to cause conflict. Microsoft still recommends the 32 bit version for most users.
Frankly, like Paul, I wonder at the necessity to do this at all. Compatibility mode means simply that it was optimised for an earlier version of Word. Later versions can cope quite adequately with the earlier files.
__________________
Graham Mayor - MS MVP (Word) (2002-2019) Visit my web site for more programming tips and ready made processes www.gmayor.com |
#12
|
|||
|
|||
One of the reasons is that old files (doc or docx+Compatibility) opened in 2013 does not display at opening all content.
Example: When you open BatchProcessDocuments Ver 2.4.dotm in 2013 x64 it displays in header: - a black text (This template ... Enter) - a red text (The various ... below) - an image After you save it in 2013, it displays more text after the image: - red text (IMPORTANT ... pairs) - black text (Enter ... ignored) |
#13
|
|||
|
|||
I think the question is why you need to process these file at all. If the files when opened one-by-one in Word 2013 do not show up properly, no conversion process is going to help.
Word files are intended to produce documents, on paper. They will not be an accurate representation of that paper document unless opened in the same version of Word using the same operating system and printer driver. See What happens when I send my document to someone else? Will Word mess up my formatting? |
#14
|
||||
|
||||
Quote:
This issue however results from a Word 2013 document being opened and then saved as 2010. The 'missing' text is still present but not displayed in compatibility mode. It is hard to see how this would occur had the document been created in Word 2010 and then ported to 2013. Word is backward compatible. It is not forward compatible.
__________________
Graham Mayor - MS MVP (Word) (2002-2019) Visit my web site for more programming tips and ready made processes www.gmayor.com |
#15
|
|||
|
|||
Quote:
So, if the Graham Mayor's add-in will be x64 compatible, this will solve my problems: - remove Compatibility Mode - fix display of 2010 files in 2013 Thank you |
Thread Tools | |
Display Modes | |
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Read the newest file in a folder, how? | DID | PowerPoint | 1 | 07-09-2014 01:40 AM |
batch file | romanticbiro | Office | 1 | 06-30-2014 06:04 PM |
How to convert a text file to an Excel file with the data format automatically? | mradmin | Excel | 6 | 10-16-2013 10:34 AM |
Batch convert multiple 32 bit xslx to 32 bit docx | mapl | Excel | 2 | 06-14-2013 05:29 PM |
Convert a file from HTML to WORD format weblayout view | gtselvam | Word | 0 | 12-02-2008 03:53 AM |