🚀 go-pugleaf

      Is this by design?




Pretty much everything Adobe does is by design, frustating as that may be at times.

acrord32 is "supposed" to stay in memory, so that it loads faster the next time you use it. It's also "supposed" to timeout after a period of non-use, and remove itself from memory - I've never seen it actually do that, however.

The AcroPDF control won't load .fdf or .xfdf documents, again by design. Adobe doesn't want you using it this way. A workaround is to use a tool like pdftk or a PDF library to embed the data into the PDF, and directly load the PDF. Reader's EULA, however, prevents you from doing this locally, stating that you can't use Reader on the same PC that creates PDF files.

So, you are pretty much forced to go the third-party route, unless you're creating the PDF on a server. Unfortunately, all the third-party viewers have shortcomings, primarily cost, poor rendition, or other limitations.