Acrobat SDK - Make a Plug-in Version Indepentent

Question

Is there a way to make an Plug-in that will be Acrobat & Reader Version Independent?
The Plug-in needs no user interface, just needs to load with whatever version of Acrobat Reader they're using.
We have a mixed environment and we want to not have to re-program the Plug-in each time Acrobat moves up a version.
We'll need access to the JavaScript to call the Plug-in's main function MyDataLoad (via DDE Channel to CRM application), if that's succesful, we may add a few more features.
TIA

Answer 1

Thanks for the prompt reply.
We currently are using Reader on the destops that print about 2% of our printing - 98% of our printing is done at the servers, which have Acrobat.
We can work around the license by not merging data at the desktops; although, not convient, our users can now add a task to any case that will print the appropriate templates at the server later in the day.
Our plug-in is for in-house use only, we have less than 25 users with Reader - Who would I ask/negotiate about how to avoid the license costs for future versions ?
I wonder if we could stay on one version of Reader for an extened period of time, our users only need to merge & print and maybe save these PDF's, any other functionality is not needed. I would just have to make sure that IT loaded the one version when they setup a new system for the one group.
Here's an overview of our project goals
1. We currently receive forms as locked PDF's from insurance carriers and we replicate them in Word to create data aware templates, this is a time consuming and exposes us to form compliance issues.
We would prefer to receive unlocked (allow field insertion & removal) and drop in our JavaScript add a few fields, or if need be, work with the fields already provided (although I like naming all my fields expr.FieldName so I can use delay expr. to enable and field value transformations)
2. An agreement that our carriers will continue to provide unlocked PDF forms for us to make data aware.
3. Add these PDF's to our DocMgt Center to enable automated printing, which currently uses MSWord merge forms. Contacts in our databse are evaludated for what should print each day, in other words out of our nearly 400 docs any combination may print for each individual contact, we're not doing a mass merge to one template, but rather logical evaluation for each case and what templates should be used in that print package.