Luke:

I think the best you could hope for would be to delete the content of the
copy.

If you put your code in an AutoOpen or DocumentOpen subroutine in the
attached macro, you could probably delete the document. But that would depend
on the attached macro being present, which you can't guarantee. Or can you?

Bear

If you *absolutely* insist <g>, have your macro:

 * Create a self-deleting batch file that does the dirty deed
 * Set Task Scheduler to run the batch file "a few/ten seconds from now"
 * Close the document

For step two, see http://groups.google.com/groups/search?q=task+scheduler+edanmo

I think you are in more danger from the training methods that cause users to
'just allow macros to run'. :( It is only a matter of time before one such
naive user brings in a  document from outside the organisation that contains
malicious code.

There is no way you can *guarantee* that users would allow the macros to
run. if you were able to guarantee it then you would be creating a virus
which will lead you into new realms of problems. Macros in distributed
documents are always fraught with problems. Why not supply them with a
template from which they can create the documents without the macros?