N
N Fiorello
Just thought someone might want to know about a problem I encountered while
testing some automation code on a machine that didn't have word activated yet.
To over simplify the process:
try
{
w = new Word.ApplicationClass();
w.Open2000();
w.PrintOut2000();
}
finally
{
w.Quit();
}
After a few unit tests I ran in a loop to watch memory... Worked great until
my 50 uses ran out. After that, I started seeing WINWORD.exe pile up in task
manager. Checking my log, I see a series of exceptions generated by Quit
saying "operation not allowed for unlicensed product"
Not activating was an oversight on a new test machine. For my customer it's
not an issue as their system's been in place for years. However don't y'all
think it's just plain STUPID to leave the exe hanging in memory and not allow
a graceful exit, even if the product hasn't been activated?
Maybe this has been fixed in later versions. Maybe it hasn't... Y'all can
do with this info what you will.
Cheers,
N-
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...664abacf&dg=microsoft.public.word.vba.general
testing some automation code on a machine that didn't have word activated yet.
To over simplify the process:
try
{
w = new Word.ApplicationClass();
w.Open2000();
w.PrintOut2000();
}
finally
{
w.Quit();
}
After a few unit tests I ran in a loop to watch memory... Worked great until
my 50 uses ran out. After that, I started seeing WINWORD.exe pile up in task
manager. Checking my log, I see a series of exceptions generated by Quit
saying "operation not allowed for unlicensed product"
Not activating was an oversight on a new test machine. For my customer it's
not an issue as their system's been in place for years. However don't y'all
think it's just plain STUPID to leave the exe hanging in memory and not allow
a graceful exit, even if the product hasn't been activated?
Maybe this has been fixed in later versions. Maybe it hasn't... Y'all can
do with this info what you will.
Cheers,
N-
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...664abacf&dg=microsoft.public.word.vba.general