C
Chip Orange
We have a 300-user network, and our users are all on Word 2002 (XP) with
SP3.
We don't have any automatic push of office updates setup by our network
admins.
We recently found a macro which aborted processing of a collection of
revisions, in a FOR EACH loop, without any error message. What we found was
that applying recent security patches via office update caused the VBA
processing to complete normally. We were wondering if this patch only fixed
the document revisions collection, or did it fix VBA processing of
collections or the FOR EACH loop, and so would effect (possibly) many other
macros (we have *a lot* of automation).
We'd like to know this in order to present to management a need to upgrade
to 2003 (requiring a centralized installation with patches), or a need to
patch 2002 up to current levels because all macros may be effected, or to
know if we don't have to worry much because this only effected the revisions
collection.
If we want an upgrade to 2003 we would be required to assure them that all
our current 2002 macros would run without problem on 2003.
If anyone can offer opinions on either this particular problem, or running
our macros on 2003, we'd appreciate the help.
BTW, I'm an application programmer, not a network admin, and they (the
admins) have a large backlog, and so the need to assess the urgency of this
2002 problem.
Thanks.
Chip Orange
SP3.
We don't have any automatic push of office updates setup by our network
admins.
We recently found a macro which aborted processing of a collection of
revisions, in a FOR EACH loop, without any error message. What we found was
that applying recent security patches via office update caused the VBA
processing to complete normally. We were wondering if this patch only fixed
the document revisions collection, or did it fix VBA processing of
collections or the FOR EACH loop, and so would effect (possibly) many other
macros (we have *a lot* of automation).
We'd like to know this in order to present to management a need to upgrade
to 2003 (requiring a centralized installation with patches), or a need to
patch 2002 up to current levels because all macros may be effected, or to
know if we don't have to worry much because this only effected the revisions
collection.
If we want an upgrade to 2003 we would be required to assure them that all
our current 2002 macros would run without problem on 2003.
If anyone can offer opinions on either this particular problem, or running
our macros on 2003, we'd appreciate the help.
BTW, I'm an application programmer, not a network admin, and they (the
admins) have a large backlog, and so the need to assess the urgency of this
2002 problem.
Thanks.
Chip Orange