I
I Need Help
Word97/WindowsXP-ProSP2
If I wasn't seeing this, I wouldn't believe it. I use an external
application that creates an rtf document. On any machine other than
the one where I run the app, the rtf documents created with this app
can be opened, edited and closed, and then word subsequently closed,
all without error.
However, on the machine where the external app is being executed, word
will open, edit and close the rtf file just fine, but once I've opened
that rtf file, even if it isn't saved or re-saved, upon exiting word:
1) Winword crashes (standard Windows error message asking me if I want
to send the report to MS)
2) The Winword instance remains visible in Task Manager and the only
way to eliminate it is from Task Manager.
This happens whether I use the command line option /a or not. This
happens with a virgin normal.dot or not. This happens with both the
/a and a virgin normal.dot.
Anybody have any ideas on what to look for?
Thanks
I Need Help
If I wasn't seeing this, I wouldn't believe it. I use an external
application that creates an rtf document. On any machine other than
the one where I run the app, the rtf documents created with this app
can be opened, edited and closed, and then word subsequently closed,
all without error.
However, on the machine where the external app is being executed, word
will open, edit and close the rtf file just fine, but once I've opened
that rtf file, even if it isn't saved or re-saved, upon exiting word:
1) Winword crashes (standard Windows error message asking me if I want
to send the report to MS)
2) The Winword instance remains visible in Task Manager and the only
way to eliminate it is from Task Manager.
This happens whether I use the command line option /a or not. This
happens with a virgin normal.dot or not. This happens with both the
/a and a virgin normal.dot.
Anybody have any ideas on what to look for?
Thanks
I Need Help