Fernando P. Nájera Cano <email@example.com> wrote on
07/08/2005 02:16:13 PM:
> Original script works too with several Office 2003. But...
> RM> 1) I moved the Word.Visible = True to the end of the
> RM> script because otherwise you get one Word window shortly
> RM> flashing.
> If you do that, in case of problems, you'll get an invisible instance
> of Word, which is not good. Users won't notice it, and they can end
> with a lot of Word.exe processes without knowing. I've got problems on
> normal.dot also when that happens.
> Maybe with better error handling it would be OK, but my vote is -1 for
> that change. I prefer Word flashing than a hidden Word instance until
> next reboot.
I agree. Although, I think that even with that line of code back in
their, if this crashes, you can still have that problem of Word not
showing. It really needs to remove all code that hides word.
This is a better version.
I have also attached a merge script. It shouldn't be included yet. I am
posting it to tap into the list's expertise.
1) I haven't figured out how to close one of the docs that I do not want
to leave open.
2) While the commands seem to work correctly, I think it sort of does
something bad to the document. The doc itself looks and behaves fine
within Word, but as an example, the compare script will never work on this
document again after the merge is saved. I suspect the problem has
something to do with the internal revision histories that Word keeps. It
is almost like you would not want Word to keep track of that anymore so
that instead you could use our compare/merge feature to do it on the fly.
Anyway, maybe someone will have an idea. I am pretty confident that the
compare script is fine and cannot do any damage.
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jul 8 20:50:15 2005
- application/octet-stream attachment: merge.vbs