🚀 go-pugleaf

I think most developers would define a bug as something which exhibits unexpected behaviour. As I mentioned in my last post, the OCX is distributed with Acrobat, as well as the Reader. That would certainly make it available as a programming tool. 

Additionally, this control worked in the previous 2 versions. If I remember correctly, there was also a small bug in version 2 or 3, which Adobe did correct. 

If the control was not meant to be used, the code could have been more easily  distributed as a dll and used as an COM add-in. 

I'm not going to try to second-guess Adobe, or anyone else. If there is another usable method, please point the poster (and myself, for that matter) to it. If not, I expect that we need to hear from Adobe that it won't be fixed, or that they are working on the problem. 

Even though I am an MVP, I don't speak for Microsoft, and I suspect you have even less stature with Adobe.  

I do speak for my clients though, and there are some solutions I am researching which use Acrobat forms over the web to enter and print contract details. Desktop applications written in VB or Access will later search and display the document. We have several possible solutions including an Access Snapshot, a Word document, and an Acrobat pdf. The pdf was until recently the front-runner because it was the "universal" solution. Now perhaps not. 

Arvin Meyer, MCP, MVP Microsoft Access