>
>Yes, I should have been more clear in this part of my questions... does a "fill-in form' created with WordXX (using the Forms toolbar and its 'text-box, check-box, etc icons) get 'properly' transformed by Acrobat such that I really have no further work to do to have an Acrobat "fill-in form"? From the sound of your answer, the fill-in areas are added after transforming the form to PDF format and so are totally outside the purview of WordXX.
>

No transformations take place. You need to add the form fields inside of Acrobat.

>Am I correct that, to use such form fully, the receiver of such forms will really need the full Acrobat product?
>

Yes and no. That's actually a more complicated question than it sounds like. It really depends on how you want the user to interact with the form data. If you are just serving up forms in a VFP app to let the user print them, then the reader is just fine. If it's not a problem for your users to Export the data, then Reader is just fine. If you really need control over Acrobat, want to automate exporting data, etc., then you will need the full version. We've used PDF's with forms to let our customers print out various state forms. They fill in the info. inside of a normal VFP form (or forms). We can then take that info and send it out to a XFDF and display the PDF that they can print. The PDF contains all of the info we passed into the XFDF. This only requires Reader.

>Finally, it does sound like lots of work save, possibly, when the WEB is the prime medium. It sounds like I would be just as well off using standard WordXX fill-in forms if the WEB is not my primary medium.
>

Again, it depends. If all of your customers have Word and they're confortable with it, then stay with it. If you need something more portable, PDF's work well.