Top Navigational Bar

Problems Saving Document While Running PC DOC
DocumentID: 604191
Revision Date: 29-Feb-96 1:30:31 PM

The information in this document applies to:
WordPerfect® 5.1 for DOS

Problem

Symptoms: When a user saves a document in WordPerfect, then tries to retrieve the document with the changes in it, one of four things may happen:
1.      The changes to the document will not show up
2.      The document will appear to be blank and, if you look at the file in List Files, it will be approximately 164 bytes in size
3.      The document will be 0 bytes in size
4.      There will be no document there Solutions: The customer was using a third-party program that was sending macro commands to WP to initiate the Save procedure. Sometimes the customer would press F7 to exit WP, say "Y" to Save Document, then press F1 to go back to the document screen. If the customer got ahead of the program, he could cancel the macro commands that the third-party program was sending. This program was causing WP to stop the Save procedure in one of the above-mentioned four places. The third-party program was changed to resolve this problem.

How/Why:
The customer was using PC DOCS, a document management program. This program was using WordPerfect's third-party interface to trap the F5, F10, F7 and Shift-F7 keys. When those keys were pressed, PC DOCS would become active, and would perform some document management facilities before returning control to WordPerfect and sending some macro commands to WP to make it save the document. PC DOCS would write information to its database about the filename of the document, the typist, long name, etc. Sometimes, the user would get a little ahead of himself, and press the F1 key while PC DOCS was trying to order WP to execute a series of macro commands. When that happened, the macro would stop and PC DOCS would force WP to stop half way through a Save procedure. Depending upon where/when the F1 key was pressed, WP would stop after it had renamed the original document to *.BK!, after it had created the new document with no information in it (0 byte file size), after it had written the document prefix (approx. 164 bytes), or the macro would stop before any of this had started and the changes to the document would not show up.

To correct the problem, PC DOCS changed the following two commands to one command:

They replaced

PutKeyInWPBuffer( MACRO_ONCANCEL );
PutKeyInWPBuffer( '~' );

with

PutKeyInWPBuffer( MACRO_CANCELOFF );

This caused WP to buffer the Cancel key when it was pressed, and not process it until after the Save procedure had completed. This was a change to the PC DOCS code, and consequently resolved the problem. PC DOCS is aware of the problem with their software, and they are going to ship an interim release of their product to resolve the problem.

Answer:

Details:


Product specifications, packaging, technical support and information (*Specifications*) refer to theUnited States retail English version only. Specifications for other versions may vary. All Specifications, claims, features, representations, and/or comparisons provided are correct to the best of our knowledge of the date of publication, but are subject to change without notice.OUR MAXIMUM AGGREGATE LIABILITY TO YOU AND THAT OF OUR DEALERS AND SUPPLIERS IS LIMITED. IT SHALL NOTEXCEED THE AMOUNT YOU PAID TO ACCESS THE INFORMATION. SEE LEGAL DISCLAIMER.