Automation Question for WORD

I have an application in which I used Automation for WORD. This has been
working for years beginning with OFFICE 97 and then OFFICE 2000. I recently
received a message from someone who trying a trial version of the
application who indicated he received a message that the program would not
work with OFFICE 2003. There is nothing exotic about my usage of
Automation -- it just opens up an existing WORD document and allows the user
to edit and save it.

Question: are there any known differences in OFFICE 2003 vs OFFICE 2000
which would require changes in using WORD Automation commands? I don't want
to go out and buy OFFICE 2003 just to find out if it is a problem with the
customer's installation as opposed to a real difference in the two products.
TIA
--E. Myron


--
To reply, change "invalid" to "net"

Dan
Thu Dec 02 12:45:21 CST 2004

Each version of Word, much like each version of FoxPro, has had its own
peccadilloes. In particular, the Word object model has been through some
hefty revisions.

I'm confused about him getting a "message saying it wouldn't work" .... is
this coming from your code? Do you know what the message ACTUALLY says
instead of "something like..."?

I can see later systems clamping down on inter-application communications
for security reasons. But that's the only thing I can really suggest without
seeing some code for what you're trying to do and knowing the ACTUAL
message.

Dan



emyron wrote:
> I have an application in which I used Automation for WORD. This has
> been working for years beginning with OFFICE 97 and then OFFICE 2000.
> I recently received a message from someone who trying a trial version
> of the application who indicated he received a message that the
> program would not work with OFFICE 2003. There is nothing exotic
> about my usage of Automation -- it just opens up an existing WORD
> document and allows the user to edit and save it.
>
> Question: are there any known differences in OFFICE 2003 vs OFFICE
> 2000 which would require changes in using WORD Automation commands?
> I don't want to go out and buy OFFICE 2003 just to find out if it is
> a problem with the customer's installation as opposed to a real
> difference in the two products. TIA
> --E. Myron

emyron
Thu Dec 02 16:00:05 CST 2004

Dan, I finally received more information from my client. The message is
generated by my program. When the following line of code is executed , I
trap for an error (as a test to be assured WORD exists). In the case of
error, I issue a message stating WORD does not exist on this system ... etc.
oWord=CREATEOBJECT("WORD.APPLICATION")
Apparently the createobject function cannot find "WORD.APPLICATION". I
would assume there is a register problem because the client indicates that
WORD (OFFICE 2003 version) exists. I'm not sure what register value(s)
have to be set in order to find WORD.APPLICATION. Any clues?
TIA
--E. Myron


"Dan Freeman" <spam@microsoft.com> wrote in message
news:%23SNVV8J2EHA.3504@TK2MSFTNGP12.phx.gbl...
> Each version of Word, much like each version of FoxPro, has had its own
> peccadilloes. In particular, the Word object model has been through some
> hefty revisions.
>
> I'm confused about him getting a "message saying it wouldn't work" .... is
> this coming from your code? Do you know what the message ACTUALLY says
> instead of "something like..."?
>
> I can see later systems clamping down on inter-application communications
> for security reasons. But that's the only thing I can really suggest
> without
> seeing some code for what you're trying to do and knowing the ACTUAL
> message.
>
> Dan
>
>
>
> emyron wrote:
>> I have an application in which I used Automation for WORD. This has
>> been working for years beginning with OFFICE 97 and then OFFICE 2000.
>> I recently received a message from someone who trying a trial version
>> of the application who indicated he received a message that the
>> program would not work with OFFICE 2003. There is nothing exotic
>> about my usage of Automation -- it just opens up an existing WORD
>> document and allows the user to edit and save it.
>>
>> Question: are there any known differences in OFFICE 2003 vs OFFICE
>> 2000 which would require changes in using WORD Automation commands?
>> I don't want to go out and buy OFFICE 2003 just to find out if it is
>> a problem with the customer's installation as opposed to a real
>> difference in the two products. TIA
>> --E. Myron
>
>

TjhenHau
Thu Dec 02 19:00:16 CST 2004

Emy,

oWord=CREATEOBJECT("WORD.APPLICATION") works just fine with Office 2003
throughout my applications.
You probably have to re-install the Office again.

HTH,
Gan, T. H.

"emyron" <myron123@adelphia.invalid> wrote in message
news:9vKdncOXy5H4DTLcRVn-gQ@adelphia.com...
> Dan, I finally received more information from my client. The message is
> generated by my program. When the following line of code is executed , I
> trap for an error (as a test to be assured WORD exists). In the case of
> error, I issue a message stating WORD does not exist on this system ...
> etc.
> oWord=CREATEOBJECT("WORD.APPLICATION")
> Apparently the createobject function cannot find "WORD.APPLICATION". I
> would assume there is a register problem because the client indicates that
> WORD (OFFICE 2003 version) exists. I'm not sure what register value(s)
> have to be set in order to find WORD.APPLICATION. Any clues?
> TIA
> --E. Myron
>
>
> "Dan Freeman" <spam@microsoft.com> wrote in message
> news:%23SNVV8J2EHA.3504@TK2MSFTNGP12.phx.gbl...
>> Each version of Word, much like each version of FoxPro, has had its own
>> peccadilloes. In particular, the Word object model has been through some
>> hefty revisions.
>>
>> I'm confused about him getting a "message saying it wouldn't work" ....
>> is
>> this coming from your code? Do you know what the message ACTUALLY says
>> instead of "something like..."?
>>
>> I can see later systems clamping down on inter-application communications
>> for security reasons. But that's the only thing I can really suggest
>> without
>> seeing some code for what you're trying to do and knowing the ACTUAL
>> message.
>>
>> Dan
>>
>>
>>
>> emyron wrote:
>>> I have an application in which I used Automation for WORD. This has
>>> been working for years beginning with OFFICE 97 and then OFFICE 2000.
>>> I recently received a message from someone who trying a trial version
>>> of the application who indicated he received a message that the
>>> program would not work with OFFICE 2003. There is nothing exotic
>>> about my usage of Automation -- it just opens up an existing WORD
>>> document and allows the user to edit and save it.
>>>
>>> Question: are there any known differences in OFFICE 2003 vs OFFICE
>>> 2000 which would require changes in using WORD Automation commands?
>>> I don't want to go out and buy OFFICE 2003 just to find out if it is
>>> a problem with the customer's installation as opposed to a real
>>> difference in the two products. TIA
>>> --E. Myron
>>
>>
>
>

TjhenHau
Thu Dec 02 19:04:21 CST 2004

Emy,

oWord=CREATEOBJECT("WORD.APPLICATION") works just fine with Office 2003
throughout my applications.
You probably have to re-install the Office again.

HTH,
Gan, T. H.

"emyron" <myron123@adelphia.invalid> wrote in message
news:9vKdncOXy5H4DTLcRVn-gQ@adelphia.com...
> Dan, I finally received more information from my client. The message is
> generated by my program. When the following line of code is executed , I
> trap for an error (as a test to be assured WORD exists). In the case of
> error, I issue a message stating WORD does not exist on this system ...
> etc.
> oWord=CREATEOBJECT("WORD.APPLICATION")
> Apparently the createobject function cannot find "WORD.APPLICATION". I
> would assume there is a register problem because the client indicates that
> WORD (OFFICE 2003 version) exists. I'm not sure what register value(s)
> have to be set in order to find WORD.APPLICATION. Any clues?
> TIA
> --E. Myron
>
>
> "Dan Freeman" <spam@microsoft.com> wrote in message
> news:%23SNVV8J2EHA.3504@TK2MSFTNGP12.phx.gbl...
>> Each version of Word, much like each version of FoxPro, has had its own
>> peccadilloes. In particular, the Word object model has been through some
>> hefty revisions.
>>
>> I'm confused about him getting a "message saying it wouldn't work" ....
>> is
>> this coming from your code? Do you know what the message ACTUALLY says
>> instead of "something like..."?
>>
>> I can see later systems clamping down on inter-application communications
>> for security reasons. But that's the only thing I can really suggest
>> without
>> seeing some code for what you're trying to do and knowing the ACTUAL
>> message.
>>
>> Dan
>>
>>
>>
>> emyron wrote:
>>> I have an application in which I used Automation for WORD. This has
>>> been working for years beginning with OFFICE 97 and then OFFICE 2000.
>>> I recently received a message from someone who trying a trial version
>>> of the application who indicated he received a message that the
>>> program would not work with OFFICE 2003. There is nothing exotic
>>> about my usage of Automation -- it just opens up an existing WORD
>>> document and allows the user to edit and save it.
>>>
>>> Question: are there any known differences in OFFICE 2003 vs OFFICE
>>> 2000 which would require changes in using WORD Automation commands?
>>> I don't want to go out and buy OFFICE 2003 just to find out if it is
>>> a problem with the customer's installation as opposed to a real
>>> difference in the two products. TIA
>>> --E. Myron
>>
>>
>
>

TjhenHau
Thu Dec 02 19:04:44 CST 2004

Emy,

oWord=CREATEOBJECT("WORD.APPLICATION") works just fine with Office 2003
throughout my applications.
You probably have to re-install the Office again.

HTH,
Gan, T. H.

"emyron" <myron123@adelphia.invalid> wrote in message
news:9vKdncOXy5H4DTLcRVn-gQ@adelphia.com...
> Dan, I finally received more information from my client. The message is
> generated by my program. When the following line of code is executed , I
> trap for an error (as a test to be assured WORD exists). In the case of
> error, I issue a message stating WORD does not exist on this system ...
> etc.
> oWord=CREATEOBJECT("WORD.APPLICATION")
> Apparently the createobject function cannot find "WORD.APPLICATION". I
> would assume there is a register problem because the client indicates that
> WORD (OFFICE 2003 version) exists. I'm not sure what register value(s)
> have to be set in order to find WORD.APPLICATION. Any clues?
> TIA
> --E. Myron
>
>
> "Dan Freeman" <spam@microsoft.com> wrote in message
> news:%23SNVV8J2EHA.3504@TK2MSFTNGP12.phx.gbl...
>> Each version of Word, much like each version of FoxPro, has had its own
>> peccadilloes. In particular, the Word object model has been through some
>> hefty revisions.
>>
>> I'm confused about him getting a "message saying it wouldn't work" ....
>> is
>> this coming from your code? Do you know what the message ACTUALLY says
>> instead of "something like..."?
>>
>> I can see later systems clamping down on inter-application communications
>> for security reasons. But that's the only thing I can really suggest
>> without
>> seeing some code for what you're trying to do and knowing the ACTUAL
>> message.
>>
>> Dan
>>
>>
>>
>> emyron wrote:
>>> I have an application in which I used Automation for WORD. This has
>>> been working for years beginning with OFFICE 97 and then OFFICE 2000.
>>> I recently received a message from someone who trying a trial version
>>> of the application who indicated he received a message that the
>>> program would not work with OFFICE 2003. There is nothing exotic
>>> about my usage of Automation -- it just opens up an existing WORD
>>> document and allows the user to edit and save it.
>>>
>>> Question: are there any known differences in OFFICE 2003 vs OFFICE
>>> 2000 which would require changes in using WORD Automation commands?
>>> I don't want to go out and buy OFFICE 2003 just to find out if it is
>>> a problem with the customer's installation as opposed to a real
>>> difference in the two products. TIA
>>> --E. Myron
>>
>>
>
>

Dan
Fri Dec 03 12:20:53 CST 2004

The class "word.application" musts be registered for you to use it. This
registration is done when Word is installed.

It sounds like a munged Office installation.

Dan


emyron wrote:
> Dan, I finally received more information from my client. The message
> is generated by my program. When the following line of code is
> executed , I trap for an error (as a test to be assured WORD exists).
> In the case of error, I issue a message stating WORD does not exist
> on this system ... etc. oWord=CREATEOBJECT("WORD.APPLICATION")
> Apparently the createobject function cannot find "WORD.APPLICATION".
> I would assume there is a register problem because the client
> indicates that WORD (OFFICE 2003 version) exists. I'm not sure what
> register value(s) have to be set in order to find WORD.APPLICATION.
> Any clues?
> TIA
> --E. Myron
>
>
> "Dan Freeman" <spam@microsoft.com> wrote in message
> news:%23SNVV8J2EHA.3504@TK2MSFTNGP12.phx.gbl...
>> Each version of Word, much like each version of FoxPro, has had its
>> own peccadilloes. In particular, the Word object model has been
>> through some hefty revisions.
>>
>> I'm confused about him getting a "message saying it wouldn't work"
>> .... is this coming from your code? Do you know what the message
>> ACTUALLY says instead of "something like..."?
>>
>> I can see later systems clamping down on inter-application
>> communications for security reasons. But that's the only thing I can
>> really suggest without
>> seeing some code for what you're trying to do and knowing the ACTUAL
>> message.
>>
>> Dan
>>
>>
>>
>> emyron wrote:
>>> I have an application in which I used Automation for WORD. This has
>>> been working for years beginning with OFFICE 97 and then OFFICE
>>> 2000. I recently received a message from someone who trying a trial
>>> version of the application who indicated he received a message that
>>> the program would not work with OFFICE 2003. There is nothing
>>> exotic about my usage of Automation -- it just opens up an existing
>>> WORD document and allows the user to edit and save it.
>>>
>>> Question: are there any known differences in OFFICE 2003 vs OFFICE
>>> 2000 which would require changes in using WORD Automation commands?
>>> I don't want to go out and buy OFFICE 2003 just to find out if it is
>>> a problem with the customer's installation as opposed to a real
>>> difference in the two products. TIA
>>> --E. Myron