LK>1.  How do you know in advance what the spelling errors of the particular
LK>person will be?
We are converting 1,000+ documents. When we've seen 'millillitre'
seven times, we figure we'll see it again. Into the table it
goes.
LK>2.  Instead of spending time creating a macro, if you know those errors, 
why
See above. We're not typing. We're correcting AFTER the typing
was done in WP51 over a period of several years by several
different staff.
LK>3.  Why not train the user to spell check the document?
We have done that for the Word project and introduced topic-
specific dictionaries.
LK>4.  Why not train the user to spell correctly in the first place?  
Like me, most users can spell. Typos occur. Significantly the
macro is caleld "FixTypos" and the associated table is
"FixTypos.doc".
From      christopher.greaves at pro-mail.com
          christopher.greaves at ablelink.org
 * 1st 2.00b #6263 * People and Computers
--- QScan/PCB v1.19b / 01-0150
---------------