Issue 79720 - Protect Document but allow input field entry - MS Word to OOo
Summary: Protect Document but allow input field entry - MS Word to OOo
Status: CLOSED DUPLICATE of issue 33737
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 2.2.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
Depends on:
Reported: 2007-07-18 00:44 UTC by noop
Modified: 2007-10-16 16:09 UTC (History)
2 users (show)

See Also:
Issue Type: FEATURE
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description noop 2007-07-18 00:44:35 UTC
Thousands of corporate & government offices have Microsoft Word documents that
are created as user fill-in forms. Typically those 'fill-in forms' transition
well when opened in OOo with the exception of the ability to the the Tab key
between input fields (this can be overcome by using Tools|Customize|Keyboard and
programing the Right & Left arrow keys to move between bookmarks), and perhaps
some slight formating issues. 

However there is a significant issue in that forms from MS Word (2003 and
earlier) that have protected text but allow user fill-in data in the input
fields, do not display the same document protection properties in OOo.

An public example of such a document is available here:
download and open the 'Ship Inward Report' document:

The document is not protected but is useful for test purposes. If you were to
open the document in MS Word 2003 you can easily protect the document text and
yet allow the user to fill in the input fields. Testing on a Windows
XPProfessional system using MSO 2003 the document protection process is as
simple as:

1. Open formc1new.doc
2. Tools|Protect Document
3. In the Protect Document sidebar, Editing Restrictions click 
   "Allow only this type of editing in the document" and select
   "Filling in forms" then "Yes, Start Enforcing Protection".
4. Save the document.

On the otherhand, if I open formc1new.doc in OOo (tested in Windows and Linux
OOo 2.2.1, 2.3dev and StarOffice8 Writer) I cannot accomplish the same behavior
- or if there is a way I've not yet figured it out. If I use Edit|Select All
then Insert|Section|Write protection it write protects the entire document,
including the input fields. 
  Interestingly enough, if I move to the input field (example the one at "Name
of ship") I cannot enter information in the input field from the keyboard and
get "Readonly content cannot be changed, No modifications will be accepted.
However, if I click on the input field with the mouse I get the input field
pop-up window showing "Edit - Text1" and I *can* enter data in the field in the
large box below that. That behavior is unacceptable and odd; why would the user
not be able to edit from the keyboard, but *can* edit from the input field pop-up?

I consider this 'feature' to be critical. MSO users simply cannot convert to OOo
without the ability to use their existing user input field forms in OOo.
Fictitious example using the example text document: NZ Customs wish to issue
their Customs officers laptops/tablets with all existing MSO forms pre-loaded.
However they do not want the officers to be able to modify text on the forms
(e.g., INWARD REPORT header etc), but do want to enable the offices to easily
fill out the forms by Tabbing (or in our case perhaps R/L arrow) between fields,
and save the form/report when completed. 

Related posts/bugs that I could find:
and of interest to me:
Comment 1 michael.ruess 2007-07-18 11:13:20 UTC
Already tracked as issue 33737.

*** This issue has been marked as a duplicate of 33737 ***
Comment 2 michael.ruess 2007-07-18 11:14:00 UTC
Closing duplicate.
Comment 3 flr 2007-10-16 09:56:58 UTC
A snapshot of the current work can be found here:

I hope its fine that I used the bugdoc from this issue for demonstration...
Comment 4 noop 2007-10-16 16:09:28 UTC
Yes! Initial test using the NZ Customs form on linux (Ubuntu Feisty 7.04) works!
Even the check boxes work as expected. Thank you so much for working on this.

Tested on a police department form - fill-in boxes work, drop-down tables work
however tabbing skips the drop-down tables so you need to use the mouse to get
to them. If you'd like I'll see if I can get permission from the police
department to send you that form for testing.