>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 ...

Hi Tracy,

Thank you very much for dropping in with real-world experience.

We currently embed the IE activeX for html display (so within the vfp interface). pdf-viewing is not cared for.

Up to now, when it comes to "on-the-fly" pdf-viewing we push an adode acrobat session (outside the vfp interface). Do you recommend displaying the pdf that thru the MS IE activeX (itself embedding the adobe viewer stuff)?

A double layer of system calls, i expect!

François