L
Lenny
To all MVP's....your assistance please
"Everything I know about macros, I learned right here", so I thought you
might be able to help. I believe this information would be beneficial to all
form developers.
Can someone point me to papers or articles written on definitively passing
customizations on to resulting documents on a network? I'm struggling to get
my head around the best and consistent method of making sure these
customizations always work.
I create electronic templates (protected Word form templates) for a large
company with thousands of users and a huge network of servers. I have
googled hundreds of times, trying to find the information I need to set up
standard work to follow to ensure that when a template has customizations,
they will always be available and work for the user. My credibility really
takes a beating when they don't work! Most of the articles are
generalizations and only go so far as to providing a consistent solution.
I always create and save the custom template before adding in code and
macros to make sure the customizations are linked to the custom template and
not Normal.dot. These templates are not only shared by our users, but with
suppliers and customers around the globe. I really need to ensure that the
code will always be there or accessible when needed.
The custom templates are stored on the network and all employees access the
masters thru Word - FILE-NEW. The code is active during the word session...
macros run, tool bars and buttons work. The user saves a copy to their
harddrive (now a doc.). The next time the user opens the file (.doc) there's
no macro to run, no tool bar or custom buttons and the Reference in the vb
editor points to "Normal"... thru my reading of the postings on the subject
here in the Discussion Groups I ascertained that a copy of the custom master
template needed to be placed in (A) the Word Startup folder, (B) the Office
Startup folder, or (C) the Office Template folder, any of which would make
the customizations available. A question here... which comes first, the
chicken or the egg. What I see happening is that once the file (.doc) is
saved to the harddrive from the master template on the network, the
connection is broken once the session is terminated and when you view the vb
editor, it points to Normal and not the custom .dot, . When the .doc is
reopened it does not / cannot access the code in the template on the network.
Should the user save a copy of the master .dot to A, B or C above first,
then use FILE-NEW to open the custom template and create a document to their
harddrive? Just as any Word .doc will reference Normal.dot.... Is there an
efficient delivery system for getting the master template to each users
correct folder rather than having to provide each user with a path that they
have to save the file to?
A couple months ago, I came across an article that indicated you could write
or copy code directly into a .doc and the code would ride along to all
additional documents (.doc's) saved from this original and have wondered
whether this would possibly be a solution. If this would work consistently,
my only issue is setting up a delivery system to the employees.
Your assistance and knowledge is appreciated as always - Regards, Lenny
"Everything I know about macros, I learned right here", so I thought you
might be able to help. I believe this information would be beneficial to all
form developers.
Can someone point me to papers or articles written on definitively passing
customizations on to resulting documents on a network? I'm struggling to get
my head around the best and consistent method of making sure these
customizations always work.
I create electronic templates (protected Word form templates) for a large
company with thousands of users and a huge network of servers. I have
googled hundreds of times, trying to find the information I need to set up
standard work to follow to ensure that when a template has customizations,
they will always be available and work for the user. My credibility really
takes a beating when they don't work! Most of the articles are
generalizations and only go so far as to providing a consistent solution.
I always create and save the custom template before adding in code and
macros to make sure the customizations are linked to the custom template and
not Normal.dot. These templates are not only shared by our users, but with
suppliers and customers around the globe. I really need to ensure that the
code will always be there or accessible when needed.
The custom templates are stored on the network and all employees access the
masters thru Word - FILE-NEW. The code is active during the word session...
macros run, tool bars and buttons work. The user saves a copy to their
harddrive (now a doc.). The next time the user opens the file (.doc) there's
no macro to run, no tool bar or custom buttons and the Reference in the vb
editor points to "Normal"... thru my reading of the postings on the subject
here in the Discussion Groups I ascertained that a copy of the custom master
template needed to be placed in (A) the Word Startup folder, (B) the Office
Startup folder, or (C) the Office Template folder, any of which would make
the customizations available. A question here... which comes first, the
chicken or the egg. What I see happening is that once the file (.doc) is
saved to the harddrive from the master template on the network, the
connection is broken once the session is terminated and when you view the vb
editor, it points to Normal and not the custom .dot, . When the .doc is
reopened it does not / cannot access the code in the template on the network.
Should the user save a copy of the master .dot to A, B or C above first,
then use FILE-NEW to open the custom template and create a document to their
harddrive? Just as any Word .doc will reference Normal.dot.... Is there an
efficient delivery system for getting the master template to each users
correct folder rather than having to provide each user with a path that they
have to save the file to?
A couple months ago, I came across an article that indicated you could write
or copy code directly into a .doc and the code would ride along to all
additional documents (.doc's) saved from this original and have wondered
whether this would possibly be a solution. If this would work consistently,
my only issue is setting up a delivery system to the employees.
Your assistance and knowledge is appreciated as always - Regards, Lenny