K
KenO
I have a template which sits on a network share and is part of a workgroup
path in word. Users create new documents from this template that contain
macro code for form automation. A user fills out the form then clicks a
button which fires my code to save the document on a different network share.
The macro also emails interested parties that there is a new form to process.
My problem occurs when the secondary users open the document, makes further
changes, then attempts to save the document, once again using macro code. Not
always, but often enough to be more than a simple nuissence, word reports a
"Disk Full" error. The disk is not full, and I have found out that it is
actually a broken temp file reference that appears under Project(doc
name)\References in the VB editor project pane. If I choose Tools\References
from the VB editor menu, I see a checkmark next to MISSING: ~temp.doc. When I
uncheck the reference to exclude it, I can then save the document normally. I
suspect that this means one of the scratch files word creates on the original
users local machine for undo, etc. occasionally gets added as a document
reference that the word running on the second users machine cant see. If I am
correct, what is the best way to guarantee that all local temp file
references are removed when the first user is ready to save the document? Is
there something beyond ActiveDocument.Save that needs to be done to ensure it
will not retain local temp file references?
path in word. Users create new documents from this template that contain
macro code for form automation. A user fills out the form then clicks a
button which fires my code to save the document on a different network share.
The macro also emails interested parties that there is a new form to process.
My problem occurs when the secondary users open the document, makes further
changes, then attempts to save the document, once again using macro code. Not
always, but often enough to be more than a simple nuissence, word reports a
"Disk Full" error. The disk is not full, and I have found out that it is
actually a broken temp file reference that appears under Project(doc
name)\References in the VB editor project pane. If I choose Tools\References
from the VB editor menu, I see a checkmark next to MISSING: ~temp.doc. When I
uncheck the reference to exclude it, I can then save the document normally. I
suspect that this means one of the scratch files word creates on the original
users local machine for undo, etc. occasionally gets added as a document
reference that the word running on the second users machine cant see. If I am
correct, what is the best way to guarantee that all local temp file
references are removed when the first user is ready to save the document? Is
there something beyond ActiveDocument.Save that needs to be done to ensure it
will not retain local temp file references?