>>I think Rick's article was aimed at a server side solution, since the target was a browser. In this case, I don't that that you'd need the writer installed on each machine, just the reader ActiveX or plug-in. Thanks for the heads up, though.
>
>You're right, it is. It's funny about acrobat licensing though, anybody that uses it on a web sever (I do) is operating on sort of a "Don't ask, don't tell" policy with regard to Acrobat. IOW, their license agreement doesn't even acknowledge the fact that the creator can be controlled programmatically (for that matter, the documentation doesn't either). Nobody knows if doing that is even legal.
>
>My lukewarm feelings toward Adobe turned ice-cold after dealing with Acrobat. They had the market cornered on pdf tools, and floundered so bad that 3rd parties had to come and fill it in with tools that do what Acrobat should have done from the beginning. Amateurs.

Thanks for the info, Erik. While I don't personally use it, it is in use here at Shaw, and this information may be helpful in the future. From Rick's article, however, I did get similar feels to your's when he wrote about version problems.