Hyperlink error from Excel 2003 to Word 2007
 

Hi,
Most of our users have Office 2007 with Windows XP. However we do
have
a handful of users who for a variety of reasons still need to use
Office 2003. These users all have the compatibility pack installed,
and it seems to generally work well with no problems.

However, one new Office 2003 user is having difficulty opening a
hyperlink from an Excel spreadsheet. The Spreadsheet is in Excel
2003,
but it links to a Word 2007 document. When he goes to click on the
hyperlink, he gets a message warning him that the file may contain
viruses and asks him if he wants to open it. If he clicks ok, he gets
a message saying "No application is associated with this file".


Yet if he browses to the folder that the file is in and double clicks
on the file, it opens with no problems. It seems to be just a problem
with the hyperlink. All other hyperlinks to Word 2003 documents work
fine.


Can anybody suggest a solution to this?


Thanks a lot


Colin

Hyperlink error from Excel 2003 to Word 2007
 

Bobby schrieb:
Hi,
Most of our users have Office 2007 with Windows XP. However we do
have
a handful of users who for a variety of reasons still need to use
Office 2003. These users all have the compatibility pack installed,
and it seems to generally work well with no problems.

However, one new Office 2003 user is having difficulty opening a
hyperlink from an Excel spreadsheet. The Spreadsheet is in Excel
2003,
but it links to a Word 2007 document. When he goes to click on the
hyperlink, he gets a message warning him that the file may contain
viruses and asks him if he wants to open it. If he clicks ok, he gets
a message saying "No application is associated with this file".


Yet if he browses to the folder that the file is in and double clicks
on the file, it opens with no problems. It seems to be just a problem
with the hyperlink. All other hyperlinks to Word 2003 documents work
fine.


Can anybody suggest a solution to this?


Thanks a lot


Colin


oh sorry, i thought i can help u, cause the problem sounded similar to a
problem that i had. But its not the same.