E
Edward
Unintentionally I have managed to bypass the macro security check which on
some machines crashes and others just continue.
All I have is a solution that uses .add to effectively copy a word object
(file) with a view to converting the spreadsheet links therein to word tables
and stripping the links to Visio files so it can be distributed as a clean
configuration independant file.
However, it all works fine and the "dumb" file is created pointing to the
Normal.dot but when it comes to re-opening the closed file any time later,
the macro securoty is bypassed as though the VB code has never left memory
and it runs OK on some machines but crashes on others.
However, if Outlook is closed down, the macro security will re-awaken and
prompt whether to run macros (depending on the security settings).
As intriguing as this is, i don't weant it to happen and would welcome any
advice or similar experience that might shed some light on what's happening.
Thanks in anticipation, Ted
some machines crashes and others just continue.
All I have is a solution that uses .add to effectively copy a word object
(file) with a view to converting the spreadsheet links therein to word tables
and stripping the links to Visio files so it can be distributed as a clean
configuration independant file.
However, it all works fine and the "dumb" file is created pointing to the
Normal.dot but when it comes to re-opening the closed file any time later,
the macro securoty is bypassed as though the VB code has never left memory
and it runs OK on some machines but crashes on others.
However, if Outlook is closed down, the macro security will re-awaken and
prompt whether to run macros (depending on the security settings).
As intriguing as this is, i don't weant it to happen and would welcome any
advice or similar experience that might shed some light on what's happening.
Thanks in anticipation, Ted