Encryption and Editing - Unable to since upgrade

Hi

I have a database that has a number of encrypted fields that users are not allowed to see. In r5 they had access to the database and were able to raise response documents. However since we upgraded to r6 they can create the form but it comes up as non editable. They still have editors access to the database, the only thing that has changed is that they are using a r6 client.

Has anyone else experienced this? Could it be that the ods is still r5, should I upgrade this to r6?

Thanks

Ang

Subject: Encryption and Editing - Unable to since upgrade

Users who don’t have the correct encryption key will not be able to save any changes that they make to the document without destroying the encrypted fields. I believe that in R5, users were allowed to enter edit mode but then they were not allowed to save the document. If I recall correctly, in ND6, this was simplified by prohibiting edit mode entirely for people who would be unable to save their changes without loss of data.

Subject: RE: Encryption and Editing - Unable to since upgrade

That leaves two questions:

  1. How do I lock down specific fields of a document (SSN, etc.) while still allowing the rest of it to be edited?

  2. Why do documents created with form inheritance turned on (Response docs, etc.) not allow editing, even though there are NO encrypted fields on them?

Thanks,

  • Shane

Subject: RE: Encryption and Editing - Unable to since upgrade

Hi

Thanks for the response. The response form they are composing does not have any encrypted fields on it is only the parent document that has these fields on.

Does this still apply?

Thanks

Angela

Subject: RE: Encryption and Editing - Unable to since upgrade

Hi Angela,

did you get any workaround for this problem?

I still have the same problem. My application works fine in R5 but not in R6 to compose or create response documents to a document with encrypted fields.

Regards

Tamer

Subject: RE: Encryption and Editing - Unable to since upgrade

I know this is years later, but I had a smiliar problem. The document I was composing inheirated values. I turned that off and could compose.

Brian