TechWhirl (TECHWR-L) is a resource for technical writing and technical communications professionals of all experience levels and in all industries to share their experiences and acquire information.
For two decades, technical communicators have turned to TechWhirl to ask and answer questions about the always-changing world of technical communications, such as tools, skills, career paths, methodologies, and emerging industries. The TechWhirl Archives and magazine, created for, by and about technical writers, offer a wealth of knowledge to everyone with an interest in any aspect of technical communications.
The Adobe Table Editor distributed with PageMaker 6.5 (at least with the
Windows version) has serious bugs that make it risky to use. An update
patch to PageMaker version 6.51 supposedly fixes things, but watch out. I'm
apparently the lucky persion to have discovered that PageMaker (including
the patched version) cannot keep track of tables imported from Adobe Table
You might be able to salvage your job by selecting and manually updating
the "link" to every every table, then printing WITHOUT FIRST SAVING the
document. (For example, reject the offer Distiller makes to save the PM
file.) You must do this even if the tables are embedded and there are no
actual linked files. If that doesn't work, you're probably SOL. However,
you can attempt copying the table data from Adobe Table and pasting into,
say, Word. Create the table in Word, copy the formatted table, and "paste
special" into PageMaker as a "Word object."
Every time you "save as" or exit from PageMaker, some or all of the links
(external or internal) to your tables will disappear. The "save" command
may or may not affect linked or embedded tables during a PM6.5/6.51
session, but you can't survive a save as or an exit. If you don't follow
this process, files with tables may print, but the tables often appear at
Adobe knows about this problem.
< @ @ >
Manny Blatt _^_
by AMREAN Associates
Information Technology, Communications, and Marketing Consultants