B
brucemc
OK, I really did search.
I run the following line on two computers:
Application.Speech.Speak "Ouch"
Both XP Pro. Both Office 2003. One computer says "ouch", the othe
errors and halts so the debugger can be brought up and points to tha
line of code.
I suspect we probably have a case where the machine that is crashin
(that is about 900 miles away) does not have athe MS Speech AP
installed, or something like that, but I am just guessing here. Anyway
is there a way that I can test for the condition so I can skip ove
running that line of code if it will cause failure, or trap the error
btw, I am using terms here that are over my head, so if you would be s
kind, please phrase your response so my four year old daughter woul
understand what to do
..
I run the following line on two computers:
Application.Speech.Speak "Ouch"
Both XP Pro. Both Office 2003. One computer says "ouch", the othe
errors and halts so the debugger can be brought up and points to tha
line of code.
I suspect we probably have a case where the machine that is crashin
(that is about 900 miles away) does not have athe MS Speech AP
installed, or something like that, but I am just guessing here. Anyway
is there a way that I can test for the condition so I can skip ove
running that line of code if it will cause failure, or trap the error
btw, I am using terms here that are over my head, so if you would be s
kind, please phrase your response so my four year old daughter woul
understand what to do
..