R
rbchase1
Greetings All,
I have a problem I can't figure out.
I have been asked to create a form for a standard report that we need
to send to our customer every week. I have created a template that
contains 90 formfields that allow the user to enter all the necessary
information. The most important functionality involed in this
template is that it makes it easy to save a copy for our internal use,
and a subset of that copy as an aditional document for our customers
use.
Because some of the end users of this template are not very computer
savvy, I have decided to lock the template from the start. I also
decided that the easiest way for me to deploy this would be to
intercept the FileSave and FileSaveAs commands and simply direct them
to my macro so I don't have to make a custom button on each users
computer.
The Macro uses data from several of the formfields to create a
standard filename, then opens a FileSaveAs dialog to allow the user to
edit the name or path of the file to be saved.
This is done a second time after some automatic editting and
protection of the document occurs.
All of this works wonderfully.
The problem is that the macro is saved in the documents created my the
macro, and the macro continues to intercept the FileSave and
FileSaveAs commands.
Is there a way that I can save the documents created by the macro in
such a way that they no longer contain or recognize the macro that is
in the template?
Thanks for your help.
Rob
I have a problem I can't figure out.
I have been asked to create a form for a standard report that we need
to send to our customer every week. I have created a template that
contains 90 formfields that allow the user to enter all the necessary
information. The most important functionality involed in this
template is that it makes it easy to save a copy for our internal use,
and a subset of that copy as an aditional document for our customers
use.
Because some of the end users of this template are not very computer
savvy, I have decided to lock the template from the start. I also
decided that the easiest way for me to deploy this would be to
intercept the FileSave and FileSaveAs commands and simply direct them
to my macro so I don't have to make a custom button on each users
computer.
The Macro uses data from several of the formfields to create a
standard filename, then opens a FileSaveAs dialog to allow the user to
edit the name or path of the file to be saved.
This is done a second time after some automatic editting and
protection of the document occurs.
All of this works wonderfully.
The problem is that the macro is saved in the documents created my the
macro, and the macro continues to intercept the FileSave and
FileSaveAs commands.
Is there a way that I can save the documents created by the macro in
such a way that they no longer contain or recognize the macro that is
in the template?
Thanks for your help.
Rob