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.
We're experiencing various "bugs" since we upgraded to the latest version of
Forehelp (including the 3.1b patch). It takes us more than 30 minutes to get
through a topic that contains bullets and various other format styles. The
wheels fall off when we perform substantial cutting and pasting between
topics and from external files. The program begins to slow down drastically,
when finally we are subjected to "New failed. Your database may be
corrupted" errors.
The above error is disastrous for us because the program adds foreign
characters to the contents of our topics. Without fail, every help project
has had this data corruption error and we had to start from scratch by
opening the .HPJ file. This allows us to recover the corrupted project but
the contaminated topics must be edited or created again. This is major down
time for us, especially when we ship our software products every two weeks.
Deadlines are fierce.
We talked to ForeFront Tech Support many times but their engineers have been
unable to recreate the problem after reviewing our project files.
We concluded that the problem may stem from our having the source files on
the network server. Once we began to work on them from the local drive, the
bullets and cutting and pasting seemed to proceed at the speed of light. We
think that another factor is that forehelp is creating temp files in the
background and causing problems while we try to write to files on the server.
We are in discussions with IS to clear this matter but they are not convinced
it's a "server" issue (lack of space on the server) that is causing
compilation and corruption problems. For obvious reasons, we want to
continue to work off the server. Does anyone know of another solution other
than working on local drive?
Is anyone else encountering these problems or are we completely off the mark?
Please email me off the list at biunnoa -at- ambest -dot- com
TIA,
Anna Biunno
Technical Writer/Editor
A.M. Best Company, Inc.
