We were using this control regularly for awhile and then switched to the webbrowser control after some strange caching issues. If you have a pdf form with fillable fields on it and you open that form two or three times and populate the fields from different data even though the data in the fields has changed and even if you generate the pdf on the fly and destroy the physical pdf afterwards, the information is cached and it is difficult to go to the last form in the stack. The activex control would display the lowest form in the stack so when the pdf form displayed the user would sometimes see the data from the first print of that pdf form for the day. The control was not released either as long as internet explorer was open on the same machine. Adobe Reader does it automatically but we could never locate code that would handle moving through the stack. This issue is posted on the Adobe forums and planetpdf as well. We do not have that problem with the webbrowser control so we use it regularly now.



>Hi Paul
>
>>I've used it. The control itself isn't supported by Adobe for use other than inside the browser (I'm not even sure if it's legal to distribute, although you could just install Acrobat Reader to get the control)...
>
>All this is changed with version 7. At least legalwise as far i can understand the annoucement. You are now entitled to call for the control in a rich client application.
>
>Check link below:
>http://www.thecodeproject.com/useritems/acroview.asp
>
>Not tested though from VFP. I'd be glad to hear that is this a workable solution!
>
>François