Dienstag, 25. Januar 2022

Washing day for PDF documents and -forms!

Like i've already explained in my blog years ago Adobe products for form creation used inserted checksum-/encryption-routines to prove if a form (created by an adobe tool) was changed by a third party pdf tool.
What does this mean? If a pdf-form or pdf-document made by an adobe tool was changed by a third party tool (fill in data and save it into the form is a modification as well) is opened by the adobe reader all form fields are not usable anymore. The form is just a simple document! Only an ugly popup-message appears telling me this:

"This document enabled extended features in Adobe Acrobat Reader. The document has been changed since it was created and use of extended features is no longer available. Please contact the author for the original version of this document."

I've made these experiences with forms created by the adobe products "InDesign" and "LiveCycle Designer"...  


These problems are now issues from the past! Now i've published a cmd-exe which removes the described restrictions and all usage rights within a second. I've called it "Unlock_ALD" (32- and 64 bit version) and it works from the commandline in Windows.

First start processing the pdf-file with Unlock_ALD and then we can work with the adobe reader and the foxit reader and any third party tool and perhaps again with an Adobe product... without these annoying restrictions anymore.

There are four ways to use Unlock_ALD:
1. Directly from the command-line.
2. Inside your batch-scripts (bat- or cmd-files).
3. From the explorer context menu via "send to...".
4. Inside your own published/distributed applications and projects via shell-syntax.

[ more details you can read on my website at "products" ... More informations regarding Unlock_ALD ]  




[All used names of trademarks, labels and companies are under the copyright of the respective companies and belongs to these companies or individuals.]  


Cheers and have a nice day,
Ingo Schmoekel