I like the idea of the script, except that a separate java script would have to be written for every form to step through every formfield and store the value somewhere. There are over 400 pdf forms with anywhere from 1 to 300 formfields on the form. If there was a way to step through all of the controls in the form and save an xml file with the formfield name and the value it would work without having to reference each individual formfield explicity it would work...sortof like stepping through the controls on a vfp form and referencing the name and value of the control. It must be a possibilit I am just not knowledgeable enough about java and Adobe to do it...

Right now we are hosting the controls on the form and the only problem is that the two controls cannot see each other's properties so changes made to the formfields in the pdf.ocx are not seen by the pdftoolkit control which has the ability to step through formfields on a form but only when read from the hardisk.

>Hi Tracy,
>
>perhaps I am totally off base here, but how about having a script inside adobe performing the equivalent of vfp buffering or (even closer) fpw scatter/gather logic ? Then the script could protocol the changes, eliminating the need to save them in acrobat. I do know that scripts are possible in adobe reader(since field based scriprs are a main source of trouble with externally developed pdf's) but I haven't checked how far support goes.
>
>Another possibility you might check is getting an object handle "inside" adobe with the help of script, and them use this handle from vfp. This "sortof" works with IE [not always stable across different versions, security changes, patches!!].
>
>regards
>
>thomas