Excel 2003 error message when opening ebedded Word 2003 doc

O

oZ

People like Garfieldnodie, cause more wasted net traffic than anyother type
of person on a use group, you too post your cross group rant which serves no
real purpose.

At least the original sender is being productive.

The Fix.

In the past i have seen this happen because Outlook was not configured or
running, simply start outlook configure it and set macro security to low and
give that a try.

The particular embeded attachment that i had problesm with was a word
document in an excel worksheet , using the =EMBED("Outlook.FileAttach",""),
this was trying to run outlook but as it was not loaded i was presented with
the error msg Simon reported.

Hope this helps.

And please accept appologies for people like Garfieldnodie.
 
O

oZ

People like Garfieldnodie, cause more wasted net traffic than anyother type
of person on a use group, you too post your cross group rant which serves no
real purpose.

At least the original sender is being productive.

The Fix.

In the past i have seen this happen because Outlook was not configured or
running, simply start outlook configure it and set macro security to low and
give that a try.

The particular embeded attachment that i had problesm with was a word
document in an excel worksheet , using the =EMBED("Outlook.FileAttach",""),
this was trying to run outlook but as it was not loaded i was presented with
the error msg Simon reported.

Hope this helps.

And please accept appologies for people like Garfieldnodie.
 
O

oZ

People like Garfieldnodie, cause more wasted net traffic than anyother type
of person on a use group, you too post your cross group rant which serves no
real purpose.

At least the original sender is being productive.

The Fix.

In the past i have seen this happen because Outlook was not configured or
running, simply start outlook configure it and set macro security to low and
give that a try.

The particular embeded attachment that i had problesm with was a word
document in an excel worksheet , using the =EMBED("Outlook.FileAttach",""),
this was trying to run outlook but as it was not loaded i was presented with
the error msg Simon reported.

Hope this helps.

And please accept appologies for people like Garfieldnodie.
 
O

oZ

People like Garfieldnodie, cause more wasted net traffic than anyother type
of person on a use group, you too post your cross group rant which serves no
real purpose.

At least the original sender is being productive.

The Fix.

In the past i have seen this happen because Outlook was not configured or
running, simply start outlook configure it and set macro security to low and
give that a try.

The particular embeded attachment that i had problesm with was a word
document in an excel worksheet , using the =EMBED("Outlook.FileAttach",""),
this was trying to run outlook but as it was not loaded i was presented with
the error msg Simon reported.

Hope this helps.

And please accept appologies for people like Garfieldnodie.
 
O

oZ

People like Garfieldnodie, cause more wasted net traffic than anyother type
of person on a use group, you too post your cross group rant which serves no
real purpose.

At least the original sender is being productive.

The Fix.

In the past i have seen this happen because Outlook was not configured or
running, simply start outlook configure it and set macro security to low and
give that a try.

The particular embeded attachment that i had problesm with was a word
document in an excel worksheet , using the =EMBED("Outlook.FileAttach",""),
this was trying to run outlook but as it was not loaded i was presented with
the error msg Simon reported.

Hope this helps.

And please accept appologies for people like Garfieldnodie.
 
O

oZ

People like Garfieldnodie, cause more wasted net traffic than anyother type
of person on a use group, you too post your cross group rant which serves no
real purpose.

At least the original sender is being productive.

The Fix.

In the past i have seen this happen because Outlook was not configured or
running, simply start outlook configure it and set macro security to low and
give that a try.

The particular embeded attachment that i had problesm with was a word
document in an excel worksheet , using the =EMBED("Outlook.FileAttach",""),
this was trying to run outlook but as it was not loaded i was presented with
the error msg Simon reported.

Hope this helps.

And please accept appologies for people like Garfieldnodie.
 
O

oZ

People like Garfieldnodie, cause more wasted net traffic than anyother type
of person on a use group, you too post your cross group rant which serves no
real purpose.

At least the original sender is being productive.

The Fix.

In the past i have seen this happen because Outlook was not configured or
running, simply start outlook configure it and set macro security to low and
give that a try.

The particular embeded attachment that i had problesm with was a word
document in an excel worksheet , using the =EMBED("Outlook.FileAttach",""),
this was trying to run outlook but as it was not loaded i was presented with
the error msg Simon reported.

Hope this helps.

And please accept appologies for people like Garfieldnodie.
 
O

oZ

People like Garfieldnodie, cause more wasted net traffic than anyother type
of person on a use group, you too post your cross group rant which serves no
real purpose.

At least the original sender is being productive.

The Fix.

In the past i have seen this happen because Outlook was not configured or
running, simply start outlook configure it and set macro security to low and
give that a try.

The particular embeded attachment that i had problesm with was a word
document in an excel worksheet , using the =EMBED("Outlook.FileAttach",""),
this was trying to run outlook but as it was not loaded i was presented with
the error msg Simon reported.

Hope this helps.

And please accept appologies for people like Garfieldnodie.
 
G

garfield-n-odie

I sincerely hope that no one will be foolish enough to set their
macro security to Low as suggested by "oZ", who can't fix his own
Windows problem but feels qualified to spew ignorant advice that
will create a huge security vulnerability in Office and Windows.
 
G

garfield-n-odie

I sincerely hope that no one will be foolish enough to set their
macro security to Low as suggested by "oZ", who can't fix his own
Windows problem but feels qualified to spew ignorant advice that
will create a huge security vulnerability in Office and Windows.
 
G

garfield-n-odie

I sincerely hope that no one will be foolish enough to set their
macro security to Low as suggested by "oZ", who can't fix his own
Windows problem but feels qualified to spew ignorant advice that
will create a huge security vulnerability in Office and Windows.
 
G

garfield-n-odie

I sincerely hope that no one will be foolish enough to set their
macro security to Low as suggested by "oZ", who can't fix his own
Windows problem but feels qualified to spew ignorant advice that
will create a huge security vulnerability in Office and Windows.
 
G

garfield-n-odie

I sincerely hope that no one will be foolish enough to set their
macro security to Low as suggested by "oZ", who can't fix his own
Windows problem but feels qualified to spew ignorant advice that
will create a huge security vulnerability in Office and Windows.
 
G

garfield-n-odie

I sincerely hope that no one will be foolish enough to set their
macro security to Low as suggested by "oZ", who can't fix his own
Windows problem but feels qualified to spew ignorant advice that
will create a huge security vulnerability in Office and Windows.
 
G

garfield-n-odie

I sincerely hope that no one will be foolish enough to set their
macro security to Low as suggested by "oZ", who can't fix his own
Windows problem but feels qualified to spew ignorant advice that
will create a huge security vulnerability in Office and Windows.
 
G

garfield-n-odie

I sincerely hope that no one will be foolish enough to set their
macro security to Low as suggested by "oZ", who can't fix his own
Windows problem but feels qualified to spew ignorant advice that
will create a huge security vulnerability in Office and Windows.
 
G

garfield-n-odie

I sincerely hope that no one will be foolish enough to set their
macro security to Low as suggested by "oZ", who can't fix his own
Windows problem but feels qualified to spew ignorant advice that
will create a huge security vulnerability in Office and Windows.
 
O

oZ

It all depends how important a document is to an individule, use the
information, if it works use it as a tempory fix, the choice is your's,
revert them back if it dont work!
 
O

oZ

It all depends how important a document is to an individule, use the
information, if it works use it as a tempory fix, the choice is your's,
revert them back if it dont work!
 
O

oZ

It all depends how important a document is to an individule, use the
information, if it works use it as a tempory fix, the choice is your's,
revert them back if it dont work!
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Macro warning in word 1
Error message: "Word found unreadable content in FILENAME. Do you want to recover the contents of this document? 0
Excel --> Word 4
I can create Publisher documents, but I can not open / read them. 0
Word docs emailed to me are opening blank (greyed screen) in Print Mode 0
Integrating information from Word to Excel (not mail merge) 1
Word 97 Password 0
You don't currently have permission to access this folder 0

Top