Hello everyone,

As much as we would like to have auto-complete disabled in our organization, we would like to KEEP it disabled. But unfortunately Adobe Reader 8 still asks users if they would like to enable the feature with this pop up message while you're filling out a form:

message: http://img515.imageshack.us/img515/7358/autocompletemessagedisanc9.jpg

Is there anyway to disable that message from appearing? We do not want this level of control accessible on certain public machines that we run.

Thanks.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I imagine this is stored in a registry setting. Set up a simple capture on a machine, select to disable it and author the result into your package. This is for v7 but I don't suppose much has changed for 8.
Answered 08/28/2007 by: VBScab
Red Belt

Please log in to comment
0
i've found this key so far, but it exists in different hives between Windows 2000 and Windows XP

Windows XP:

HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\8.0\FormsPrefs
-bUserAskedToEnableAutoComplete

Windows HKEY_USERS\S-1-****************\Software\Adobe\Acrobat Reader\8.0\FormsPrefs
-bUserAskedToEnableAutoComplete

Windows 2000:

Windows HKEY_USERS\S-1-****************\Software\Adobe\Acrobat Reader\8.0\FormsPrefs
-bUserAskedToEnableAutoComplete

And it does not exist it at all on my Windows XP laptops.

yikes...
Answered 08/28/2007 by: appzilla
Senior Yellow Belt

Please log in to comment
0
And it seems that this FormsPrefs key only appears after you're prompted by the message. Its probably used as a marker to store the users form preferences.
Answered 08/28/2007 by: appzilla
Senior Yellow Belt

Please log in to comment
0
The Win2K keys are the same as the XP ones: HKEY_CURRENT_USER is "shorthand" for HKEY_USERS\[user GUID which begins S-1-...]

Don't worry about them not being there: you need to create them in your package, thus bypassing the need to wait for Reader to do it after it's popped up the dialog. Do you see? By creating these keys in your package, you're fooling Reader into thinking it did it already and thus won't pop up the dialog.
Answered 08/28/2007 by: VBScab
Red Belt

Please log in to comment
0
You sir, are absolutely right.

thank you very much. I will try that.
Answered 08/28/2007 by: appzilla
Senior Yellow Belt

Please log in to comment
0
actually if HKCU is not permanent, and HKEY_USER depends on a specific users GUID

how am i supposed to deploy this fix over a broad range?

javascript?
Answered 08/28/2007 by: appzilla
Senior Yellow Belt

Please log in to comment
0
Windows Installer and whichever packaging tool you're using will sort this out for you. Don't use the GUID-style entry: just create the necessary structure and entries in HKEY_CURRENT_USER using Wise or InstallShield (I figure you must be using one or the other). When you run the package, Windows Installer will create the entries under the "right" user's HKEY_CURRENT_USER tree.
Answered 08/28/2007 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity