Hello Jim,
There are really only a few ways that you can avoid the "Read-Only" prompt
with Word Automation:
1) Using the ReadOnly parameter = True of the Documents.Open method.
(Note:this should work for you but since you explain that you've already
tried this
there is another point I'll make in a moment)
2) Set Application.DisplayAlerts = wdAlertsNone to suppress alerts and take
the default action.
3) Use Windows APIs to dismiss dialogs that appear during Automation.
Each of the three points above are discussed in this Knowledge Base article:
Q259971 - HOWTO: Dismiss a Dialog Displayed by an Office Application with VB
http://support.microsoft.com/support/kb/articles/Q259/9/71.asp
As I mentioned, using the ReadOnly parameter = True should avoid this
prompt; I don't know of any known issues where this would fail. However,
you may see unexpected behavior when Automating Word if you do not qualify
all of your calls to Word methods and properties. If you had unqualified
calls, Word 97
might let you get away with it where Word 2000 will not (due to changes in
instancing). If your VB project has a reference to the Word type library,
not qualifying a method/property for Word is an easy mistake to make because
it does not generate a compile error. For posterity, it might be good to
confirm that all your calls to Word methods and properties are qualified.
Word Automation calls that should be qualified include "ActiveDocument",
"Selection", and InchesToPoints" (there are many others but these are the
ones that most commonly trip folks up). For details, see the following:
Q189618 - PRB: Automation Error Calling Unqualified Method or Property
http://support.microsoft.com/support/kb/articles/Q189/6/18.asp
From the case notes, it is not clear how the server is involved. If you are
Automating Word *on* the server, there are some issues you should be aware
of
-- one of which is a situation where dialogs might appear unexpectedly and
wait for user input (which can hang the server application if the server is
unattended and/or Word is not visible). While Automating Word on an
interactive client is perfectly fine, we do not recommend Word Automation
(97, 2000, or 2002) on the server. This article covers this topic in greater
detail:
INFO: Considerations for Server-Side Automation of Office
http://support.microsoft.com/support/kb/articles/Q257/7/57.asp
Taimur Mughal [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
OR if you wish to include a script sample in your post please add "Use of
included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm"
