How does the structure/behavior of a .doc with a macro embedded di

[EC3CRR]

We are using a document management system and are having problems doing a
'file save as' back to the system only when there is a word document that has
a macro attached to it. The macro can be as simple as recording the typing
of 'hello'.

What could be the difference between the way a macro file is physically or
behaves on saving that could cause this?

 

[Tony Jollans]

Prior to 2007 the only ay you would see a difference would be by
unscrambling the contents. Even in 2007, that is essentially true (although
macro-enabled documents are .docM, rather than .docX, files). What is your
document management system trying to do, I wonder?

 

[EC3CRR]

It's trying to post the file back to it's file server, but it hits a share
violation. Weird thing is it doesn't happen with a plain file....I know the
macro file is bigger, and sometimes takes longer to load, but not when it's a
tiny macro.

Thanks for writing back!

 

[Doug Robbins - Word MVP]

I would suggest that you seek assistance from the supplier of the document
management system.

--
Hope this helps.

Please reply to the newsgroup unless you wish to avail yourself of my
services on a paid consulting basis.

Doug Robbins - Word MVP, originally posted via msnews.microsoft.com

 

[Gordon Bentley-Mix on news.microsoft.com]

I second Doug's suggestion and would add the following - not all of which may
be applicable to your situation:

In my experience, many document management systems (EDMS) modify documents
to break the link between the document and its template. This sometimes
causes problems when re-opening the document because any macros in the
template are no longer available in the document.

In addition, EDMSs tend not to work very well for storing and launching
templates that contain macros - especially AutoNew or Document_New type
macros. This is because when the EDMS creates a "new" document from the
template, it actually just creates a copy of the template and opens it as a
document. Thus no Document_New event ever fires and the macros are not
triggered.

Finally, macros generally requires references to resources in the Word
environment to run properly. Depending on the macro, some of these resources
are actually "employed" when the document is opened. Word is fine with this
because it "knows" that it's the one using the resource and is happy to share
it. However, it's possible that when the EDMS is saving the document, it's
attempting to use the same resource that Word is already using via the macros
- and thus the sharing violation.

So to answer your original question, it's not really a matter of how the
macro-enabled document is structured or behaves, but rather how macros affect
the interaction of the document with the EDMS. And this is something that can
probably only be addressed by the EDMS vendor, as they will have the "insider
knowledge" of how the EDMS works behind the scenes.
--
Cheers!

Gordon Bentley-Mix
Word MVP

Please post all follow-ups to the newsgroup.

Read the original version of this post in the Office Discussion Groups - no
membership required!