How To Convert Thousands of Works 7.0 Files to Word 2007 Simultaneously

J

Jeffrey L. Hook

Graham:
It's probably a bit late to help you, but I believe I have resolved the
security warning issue. The revised version is on my web site.

You've helped me tremendously.

I'd now like to try to help other users who will find this thread in the
future and who'll want to complete their own "mass" or "batch" conversions
of large numbers of files. I'd therefore like to clarify two remaining
topics. I've captioned them and I've put clarification of the first topic
below my signature, as optional text:

1. PROBLEM OF THE INTERRUPTION OF THE MACRO'S AUTOMATIC OPERATION BY THE
SECURITY-WARNINGS:

I used my "semi-manual" method to convert nearly 636 WPS files which had
last been modified in Works 4.0 and in Works 4.5a. I only afterward
wondered if I'd "blown it": You say this at the instructions page for your
batch converter:

http://www.gmayor.com:80/Works_Batch_Converter.htm

+++++

....The add-in requires the Works converter to be installed prior to running
the macro. Word 2007 comes with a converter that will open recent versions
of Works WPS format. Older Works file versions require earlier converters
which you can download from the downloads page of this site...

+++++

You also say this at your "Downloadable files" page, at the top of the page,
in your discussion of the batch converter:

http://www.gmayor.com/downloads.htm

+++++

....Batch converter for Works WPS format to DOCX - 27kb - An add-in for Word
2007 to batch convert Works WPS format documents to Word 2007 DOCX format
and a dedicated page of user instructions. For old Works documents, you may
also require the Works converters that you will find below...

+++++

Two questions about this topic:

A. Could I have eliminated this problem entirely by running your old-file
converter in order to convert the Works 4.0 and 4.5a files first, before I
ran the batch-converter?

B. Did you solve the security warning problem by incorporating your
old-file conversion code into the batch converter?

2. OBSERVING THE CODE OF THE LATEST VERSION OF THE BATCH CONVERTER:

I've also downloaded this version, although I've not run it because, as you
realized, the first version completed my project for me.

I would like to observe the code of this version, however.

I previously reported how I used the "Edit" button on the right side of the
"Macros" dialog from the left end of the Developer ribbon to view the code
of the first batch converte in the VBA GUI. I see that the current version
is an Add-in and that it appears on the Add-in ribbon, rather than on the
Developer ribbon. Is it possible to view the code of the current macro?
Can you explain how I can do this?

Thanks for all your excellent assistance.

Jeff Hook, NJ, USA (**Optional** clarification of the security warning
problem is below.)

I explained in my message of April 30th how conversion of older Works WPS
files interrupted the *automatic* operation of the batch-conversion macro.
A security warning was displayed for each old file. The warning explained
"This file needs to be opened by the Works 4.0 for Windows text converter,
which may pose a security risk if the file you are opening is a malicious
file." The warning incorporated this Help text:

+++++

You are trying to open a file with a converter that may pose a security
risk. The following converters, which were included in earlier versions of
Microsoft Office Word, may pose a security risk if the file that you are
opening is not from a trusted source:



Text with Layout (*.ans)

Microsoft Excel Worksheet (*.xls)

Microsoft Word 6.0/95 (*.doc)

Microsoft Word 4.0 for Macintosh (*.mcw)

Microsoft Word 5.0 for Macintosh (*.mcw)

Microsoft Word 5.1 for Macintosh (*.mcw)

Microsoft Word 2.x for Windows (*.doc)

Microsoft Works 2000 (*.wps)

**Microsoft Works 4.0 for Windows (*.wps)**



For more information, see Microsoft Knowledge Base article 837011.



+++++

The Knowledge Base article is at:

http://support.microsoft.com/?kbid=837011

No "Yes to all" response option was given. It was necessary to left-click
the "Yes" button in each warning for each file. The batch-conversion macro
couldn't operate automatically until all of these old files were converted.

Clicking the "Yes" button on the security warning allowed me to open each
file in Word 2007, where I was then able to convert, save, and close each
file with a single mouse click on my own "Convert-Save-Close" macro, for
which I'd installed an icon button on the Word 2007 Quick Access Toolbar.
This therefore could be regarded as a "semi-manual" conversion method: It
was necessary to convert each file individually; files couldn't be converted
automatically, in an "unattended" process, but part of the process was
automated by my own simple macro.

The security warnings referred specifically to the "Works 4.0 for Windows
text converter" but I suspected the warnings were also shown for Works 4.5a
files. My original OEM copy of Works 4.0 was upgraded to Works 4.5a by the
Microsoft Y2K CD in late 1999 and I installed Works 6.0 on February 3rd,
2001. I used my desktop search engine to search for all WPS files which had
been modified before March 1st, 2001, I sorted the list of files by
modification date. I found that files which had still last been modified in
Works 4.0 and in Works 4.5a files produced the security warning. Files
which had been modified after Works 6.0 was installed didn't produce the
warning.

JLH

It's probably a bit late to help you, but I believe I have resolved the
security warning issue. The revised version is on my web site.
--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP


<>>< ><<> ><<> <>>< ><<> <>>< <>><<>

(snipped)
 
G

Graham Mayor

Jeffrey said:
Two questions about this topic:

A. Could I have eliminated this problem entirely by running your
old-file converter in order to convert the Works 4.0 and 4.5a files
first, before I ran the batch-converter?

No. The old converters on my web site merely allow Word to open the older
files. You would have got the security warning with these files when running
the macro I originally supplied.
B. Did you solve the security warning problem by incorporating your
old-file conversion code into the batch converter?

No - I found a means of suppressing the warning. The macro is independent of
the converters.
I previously reported how I used the "Edit" button on the right side
of the "Macros" dialog from the left end of the Developer ribbon to
view the code of the first batch converter in the VBA GUI. I see that
the current version is an Add-in and that it appears on the Add-in
ribbon, rather than on the Developer ribbon. Is it possible to view
the code of the current macro? Can you explain how I can do this?

You will need the Office 2007 Custom UI Editor to view and edit the code
relating to the Ribbon. I moved the button to the Add-ins ribbon as that
seemed a more logical place for it.
http://microsoft-office-2007-custom-ui-editor.software.informer.com/
Thanks for all your excellent assistance.

You are welcome

--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP


<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top