Word 2000 to Word 2013 conversion...
Recently replaced a few computers where users were using Office 2000 in one case & Office 2003 in another. Both are now using Office 2013 & both have quite a few .doc files that need to be .docx for 'ease of use', for lack of a better term! I've seen questions here referring to VBS scripts or the MigrationPlanningManager, but really don't understand working with vbs scripts. These docs aren't all in one folder. In one case they are on a server, but in many sub directories & in the other, on one computer shared out in a workgroup. Is there a vbs for dummies, or an easy way to do this?
ASKER
A couple of questions, can I just replace them in their current directory? How can I get it to scan sub directories?
I'm assuming (uh-oh...) it will only affect any word docs in the process? Not jack up any excel, pdf, jpg or anything else it may encounter along the way?
I'm assuming (uh-oh...) it will only affect any word docs in the process? Not jack up any excel, pdf, jpg or anything else it may encounter along the way?
Yes, this will only affect Word files. Good of you to ask, Microsoft tends to mess things up like that lol.
You can put the source and destination filepath as the same thing without issue as Windows will see the files as two different files because the extensions are different (.doc and .docx)
You can put the source and destination filepath as the same thing without issue as Windows will see the files as two different files because the extensions are different (.doc and .docx)
ASKER
So will I wind uo with a folder full of doc & docx files?
Based on that article, here's my ini file I modified & it doesn't appear to be doing anything.
What am I missing, other than understanding of writing scripts?
[Run]
;LogDestinationPath=C:\doc
;TimeOut = 3
[ConversionOptions]
; FullUpgradeOnOpen: if set to 1, Word documents will be fully converted to the OpenXML format
; if set to 0 (default), Word documents will be saved in the OpenXML format in compatibility mode
FullUpgradeOnOpen=0
CABLogs=0
MacroControl=0
[FoldersToConvert]
fldr=C:\docxtest\
[ConversionInfo]
SourcePathTemplate=*\*\*\*
DestinationPathTemplate=C:
Based on that article, here's my ini file I modified & it doesn't appear to be doing anything.
What am I missing, other than understanding of writing scripts?
[Run]
;LogDestinationPath=C:\doc
;TimeOut = 3
[ConversionOptions]
; FullUpgradeOnOpen: if set to 1, Word documents will be fully converted to the OpenXML format
; if set to 0 (default), Word documents will be saved in the OpenXML format in compatibility mode
FullUpgradeOnOpen=0
CABLogs=0
MacroControl=0
[FoldersToConvert]
fldr=C:\docxtest\
[ConversionInfo]
SourcePathTemplate=*\*\*\*
DestinationPathTemplate=C:
Ok, it took some digging but I think I figured out your issue.
With newer versions of windows, the C:\ drive is more protected. Since Microsoft wrote this conversion utility with crappy error handling (surprise, surprise) the utility doesn't tell you that it can't write to the root of the C:\ drive.
I moved the test folder to the desktop and BAM! it worked perfectly. Try that and let me know what happens.
With newer versions of windows, the C:\ drive is more protected. Since Microsoft wrote this conversion utility with crappy error handling (surprise, surprise) the utility doesn't tell you that it can't write to the root of the C:\ drive.
I moved the test folder to the desktop and BAM! it worked perfectly. Try that and let me know what happens.
ASKER
The ; at the beginning of the line comments it out (that's the correct term, right?)
I don't care about logs, etc., but I'm running this, a command prompt window flashes briefly & docs seem to be unchanged. The folder has a dozen or so word 2000 & word 2003 docs. When I open one, it comes up in compatibility mode. I have found that I can go to file>convert & it saves the doc, replacing the original one, which I'm thinking is going to be what I tell users to do, haha!
I do appreciate your help & patience, though!
Where am I going wrong with this ini file?
[Run]
;LogDestinationPath=C:\Use
;TimeOut = 3
[ConversionOptions]
; FullUpgradeOnOpen: if set to 1, Word documents will be fully converted to the OpenXML format
; if set to 0 (default), Word documents will be saved in the OpenXML format in compatibility mode
FullUpgradeOnOpen=1
CABLogs=0
MacroControl=0
[FoldersToConvert]
fldr=C:\Users\Mikey\Deskto
[ConversionInfo]
SourcePathTemplate=*\*\*\*
DestinationPathTemplate=C:
I don't care about logs, etc., but I'm running this, a command prompt window flashes briefly & docs seem to be unchanged. The folder has a dozen or so word 2000 & word 2003 docs. When I open one, it comes up in compatibility mode. I have found that I can go to file>convert & it saves the doc, replacing the original one, which I'm thinking is going to be what I tell users to do, haha!
I do appreciate your help & patience, though!
Where am I going wrong with this ini file?
[Run]
;LogDestinationPath=C:\Use
;TimeOut = 3
[ConversionOptions]
; FullUpgradeOnOpen: if set to 1, Word documents will be fully converted to the OpenXML format
; if set to 0 (default), Word documents will be saved in the OpenXML format in compatibility mode
FullUpgradeOnOpen=1
CABLogs=0
MacroControl=0
[FoldersToConvert]
fldr=C:\Users\Mikey\Deskto
[ConversionInfo]
SourcePathTemplate=*\*\*\*
DestinationPathTemplate=C:
ASKER
One other oddity I've experienced is at one location docs are all on a server.
One user (Vista, Office 2007)_ can open a doc & it opens, displays, etc., just fine.
Another user (one with the recently replaced XP, Office 2007, now Win7, Office 2013) can open the same doc & it comes up in compatibility mode?
What's up wit dat?
One user (Vista, Office 2007)_ can open a doc & it opens, displays, etc., just fine.
Another user (one with the recently replaced XP, Office 2007, now Win7, Office 2013) can open the same doc & it comes up in compatibility mode?
What's up wit dat?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The article tells you to download some utlities, definitely do. When I used this utility it didn't work when I decided to "do it my own way" haha
hth