Document protection

You could add a password which should lock the document;
          then when the receiver reads the document, he should be able to
copy it to his machine, make any additions & send back to you;
             then you can make the changes to the table & re-send/upload.

       I don't know the details as to how this would work;
          whenever I upload anything, I always click on 'only those with
the link' can open which keeps prying roving eyes from seeing.

       Hoping this helps to some degree,

Sorry for the late reply, anne-ology, I haven't been able to get back to this.

This is an internal use document only, so once it is finished, there will be no need to change the document, unless some needed modification is discovered later.

The fill in fields will be populated with information that changes with each ticket in our work order system. I'm trying to prevent the form from becoming mangled unintentionally.

So what I need, as I said in the original post, is a document that will be "locked", but you can still complete the fields. When that is accomplished, the file will be marked read only so when it's saved with new information, a new filename will be required.

I always use PDF fillable forms for this kind of thing...

Hi *,

So what I need, as I said in the original post, is a document
that will be "locked", but you can still complete the fields.
When that is accomplished, the file will be marked read only so
when it's saved with new information, a new filename will be
required.

I always use PDF fillable forms for this kind of thing...

Think this won't work. PDF-form-document could be saved more than one
times with the same name. The saving of the form must create a new
document, for example a *.pdf-file without form-elements.

I would prefer a Wrtier-form-document, which should be
write-protected. You could write in the form-elements of the form, but
couldn't change it except you will save it as a new form with a new
name. If the form is filled a button should be pressed - the content
should be exported with macro to a separate *.pdf-document. Have made
something like this for the German Base-Handbook with reports of a
Base-document.

Regards

Robert

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi *,

So what I need, as I said in the original post, is a document
that will be "locked", but you can still complete the fields.
When that is accomplished, the file will be marked read only so
when it's saved with new information, a new filename will be
required.

I always use PDF fillable forms for this kind of thing...

Think this won't work. PDF-form-document could be saved more than one
times with the same name. The saving of the form must create a new
document, for example a *.pdf-file without form-elements.

Once the form is created, and the info in the form is write protected, save the file. The mark the file as read only. I think that will force a name change when you try to save it.

Hi Ken,

Once the form is created, and the info in the form is write
protected, save the file. The mark the file as read only. I
think that will force a name change when you try to save it.

I have just used *.pdf-forms for my children. Had to fill in all data,
had to save it, had to change it ... I could always write the new form
data over the old form data and the new form data would be saved. The
old data had been gone, if I won't chose "Copy save as", but only
"Save as".

I have created an example how to do this job with a Writer-file:
http://robert.familiegrosskopf.de/download/Formular_ohne_DB.odt

It's in German language, but there is not much special German content.

You have to enable macro-executing for this file. The form should be
opened as write-protected. You could also write-protect it through
your system.

Fill in some content. If you press "Speichern" the file will be saved
as a *.pdf in the same directory as "Formular_ohne_DB.odt". The *.pdf
will be saved without a working form, so the content is (a little bit)
protected. The name of the file will be created from the field
"Vorname". Best would be the name is created in a database by an ID,
which is unique. So the exported files will all get different names.

Regards

Robert

Thanks, Robert.