J
JeffP->
I started with a template that uses a bunch of interesting stuff to populate
its mergefields, now I'd like to put that code into an addin and not have to
maintain my code in multiple templates. To that end, I originally started
w/an ini class to read an ini file and match the doc template name with
instructions on what sProc to use, data server name, database name etc. I
also used a doc property to match the ini value with the docprop and do
nothing if there isn't a match so that my code doesnt exec for any other doc
or template.
My template works great, it uses DDE to get the current record num from my
application, then the ini to get instructions, then queries the database via
sProc and updates it's matching docprops with the recordset fieldnames, then
updates the fields.
BUT, when I place the same code in an addin saved in the startup folder,
it's listed in the addins in Word, and will exec if I manually exec the main
macro, but unlike the template won't update on open/new - which I need
because I have automated printing which conditionally prints any one of 600
templates including this one, so no one will be there to exec the macro...
This is our first merge project using multiple addins and merging data
external to our main database.
Any hints or things to do or not to make two addins play nice?
its mergefields, now I'd like to put that code into an addin and not have to
maintain my code in multiple templates. To that end, I originally started
w/an ini class to read an ini file and match the doc template name with
instructions on what sProc to use, data server name, database name etc. I
also used a doc property to match the ini value with the docprop and do
nothing if there isn't a match so that my code doesnt exec for any other doc
or template.
My template works great, it uses DDE to get the current record num from my
application, then the ini to get instructions, then queries the database via
sProc and updates it's matching docprops with the recordset fieldnames, then
updates the fields.
BUT, when I place the same code in an addin saved in the startup folder,
it's listed in the addins in Word, and will exec if I manually exec the main
macro, but unlike the template won't update on open/new - which I need
because I have automated printing which conditionally prints any one of 600
templates including this one, so no one will be there to exec the macro...
This is our first merge project using multiple addins and merging data
external to our main database.
Any hints or things to do or not to make two addins play nice?