G
gardner.bob
I am using Access to email a report to a number of users. They open
the report by going to their email provider web email page using IE.
The email report shows up just fine as an attachment to the email. The
attachment is named "report.rtf" since I selected the RTF format in
Access. The problem appears to be with Windows XP users (I think).
They click on the attachment and get the IE Save/Open dialog box. In
the box, the file name shows up as "report.doc" instead of
"report.rtf". If they choose to save the report, it is saved as a .doc
file and they can then open it. If they choose to open it directly
from IE, the file is attempted to be opened as "report.doc" and of
course this file does not exist and the user gets the appropriate
message and is frustrated.
Why is IE changing the file type? Is this some type of feature or am I
doing something wrong? Is there something I can do to make this easier
for the user?
The application was written in Access 2000 under Windows 2K but is
being used by users with Access 2000, 2002, and 2003 under Windows 98
and XP. So far the only users who seem to be having a problem are
those with XP.
Thanks for any ideas you might have.
Bob Gardner
the report by going to their email provider web email page using IE.
The email report shows up just fine as an attachment to the email. The
attachment is named "report.rtf" since I selected the RTF format in
Access. The problem appears to be with Windows XP users (I think).
They click on the attachment and get the IE Save/Open dialog box. In
the box, the file name shows up as "report.doc" instead of
"report.rtf". If they choose to save the report, it is saved as a .doc
file and they can then open it. If they choose to open it directly
from IE, the file is attempted to be opened as "report.doc" and of
course this file does not exist and the user gets the appropriate
message and is frustrated.
Why is IE changing the file type? Is this some type of feature or am I
doing something wrong? Is there something I can do to make this easier
for the user?
The application was written in Access 2000 under Windows 2K but is
being used by users with Access 2000, 2002, and 2003 under Windows 98
and XP. So far the only users who seem to be having a problem are
those with XP.
Thanks for any ideas you might have.
Bob Gardner