F
frheko
I have both Outlook 2000 and GW 6.5.1 installed and I use both programs.
Whenever I try to open an email that has an attached email with .msg or
..msg.msg extension from within Outlook, GW starts up and the attachment
never opens. I recently upgraded to 6.5.1 from an earlier version and I
didn't have the problem prior to the upgrade. For example, when opening
emails (in Outlook) that were attached to other emails, GW would not open,
rather, the attached messages would open and display correctly in Outlook.
The only workaround I have for the current problem is to save the attached
*.msg to the desktop as a searate file and then open it; it then opens
without opening GW. Any ideas how to prevent GW from starting when I'm
trying to open the attachment messages in Outlook?
Reassociating the .msg extension with Outlook.exe is ineffective. I noticed
that when I saved the attached message to the desktop, the extension was
listed as "*.msg.msg" (2X). THe new groupwise program also has some more
sophisticated msg attachment viewing that might be contributing to this
problem.
Any help is appreciated.
Thanks
fhk
Whenever I try to open an email that has an attached email with .msg or
..msg.msg extension from within Outlook, GW starts up and the attachment
never opens. I recently upgraded to 6.5.1 from an earlier version and I
didn't have the problem prior to the upgrade. For example, when opening
emails (in Outlook) that were attached to other emails, GW would not open,
rather, the attached messages would open and display correctly in Outlook.
The only workaround I have for the current problem is to save the attached
*.msg to the desktop as a searate file and then open it; it then opens
without opening GW. Any ideas how to prevent GW from starting when I'm
trying to open the attachment messages in Outlook?
Reassociating the .msg extension with Outlook.exe is ineffective. I noticed
that when I saved the attached message to the desktop, the extension was
listed as "*.msg.msg" (2X). THe new groupwise program also has some more
sophisticated msg attachment viewing that might be contributing to this
problem.
Any help is appreciated.
Thanks
fhk