K
Konrad Schiemert
Hello NewsGroup,
I start Word2007 out of a C++-Code with automation (by calling
CoGetClassObject and .CreateInstance).
This works well with all versions of Word except for Word2007. With Word2007
I get an error message,
if Word is already running and a word-file is already open.
A message (similar to this in German) comes right after the function
CoGetClassObject has been called:
" XXXX.dotm is in use by 'YYYYY' and cannot be changed.
Would you like to
1. Open read-only...
2. Create a local copy...
3. Get notified, when the original is available...?",
where XXXX.dotm is a user-defined template. (The file is not
write-protected, i.e. it is not read-only).
How can I get rid of this message-box? Is there an option in Word or a
registry entry, which I can use
to define certain options as default options so that this message stops
popping up again. (The function
CoGetClassObject does not accept any application-specific or general
options.)
Kind regards,
Konrad Schiemert
I start Word2007 out of a C++-Code with automation (by calling
CoGetClassObject and .CreateInstance).
This works well with all versions of Word except for Word2007. With Word2007
I get an error message,
if Word is already running and a word-file is already open.
A message (similar to this in German) comes right after the function
CoGetClassObject has been called:
" XXXX.dotm is in use by 'YYYYY' and cannot be changed.
Would you like to
1. Open read-only...
2. Create a local copy...
3. Get notified, when the original is available...?",
where XXXX.dotm is a user-defined template. (The file is not
write-protected, i.e. it is not read-only).
How can I get rid of this message-box? Is there an option in Word or a
registry entry, which I can use
to define certain options as default options so that this message stops
popping up again. (The function
CoGetClassObject does not accept any application-specific or general
options.)
Kind regards,
Konrad Schiemert