U
Usenet
Hi,
I have been asked to add functionality to a global template (Word 2003,
all XP systems).
What is needed is a mechanism to automatically update template
documents, all of which are stored locally on the users systems. I need
to do this quietly in the background, so that for users, disruption of
performance is minimal. The idea is to compare modification dates of
local templates to the ones in a central template storage location, and
copy them to the local system if necessary.
I am thinking about the following approach:
use OnTime or use the Windows API to schedule a routine that does the
comparing/copying of files. I found a good resource at cpearson.com for
this.
I could do all the file-comparing stuff from the VBA code itself, or by
calling (from VBA) an external stand-alone VBS script, residing in the
central storage location. A VBS script would be easier to maintain, and
there would be minimal impact for end-users. On the other hand, it would
be an extra 'thingie', and doing the comparing/copying from within the
macro itself might be more 'natural'. However, I am worried the latter
approach would disrupt whatever the users are doing; using DoEvents can
alleviate that but still.
I would appreciate input on what you think is the best way to go.
regards,
arno
I have been asked to add functionality to a global template (Word 2003,
all XP systems).
What is needed is a mechanism to automatically update template
documents, all of which are stored locally on the users systems. I need
to do this quietly in the background, so that for users, disruption of
performance is minimal. The idea is to compare modification dates of
local templates to the ones in a central template storage location, and
copy them to the local system if necessary.
I am thinking about the following approach:
use OnTime or use the Windows API to schedule a routine that does the
comparing/copying of files. I found a good resource at cpearson.com for
this.
I could do all the file-comparing stuff from the VBA code itself, or by
calling (from VBA) an external stand-alone VBS script, residing in the
central storage location. A VBS script would be easier to maintain, and
there would be minimal impact for end-users. On the other hand, it would
be an extra 'thingie', and doing the comparing/copying from within the
macro itself might be more 'natural'. However, I am worried the latter
approach would disrupt whatever the users are doing; using DoEvents can
alleviate that but still.
I would appreciate input on what you think is the best way to go.
regards,
arno