How can I get an attachment in Outlook 2007 to save?

I have a few people, who when trying to save an attachment, get a message
"Cannot save the attachment." This extends over different files (doc, xls,
pdf). There ends up a Zero byte file, where they were trying to save.
I tested to see if it was something like the Outlook Temporary folder
problem - When a file is opened 99 times, in Outlook, the file can no longer
be saved, until you find the Hidden OLKxxxx (or similar) file, that you had
to go to Regedit to find.
I removed ALL files from this folder. But, problem still there. People using
Ms-Office 2007 Professional, with Windows XP (not sure if Sp2 or Sp3).
They have been having this problem for a week. They originally were
wondering if it had anything to do with the bad McAfee definition update.
Thanks for any help.

Seems there is more to this. It isn't just a problem with Outlook 2007. It is
a problem with Office 2007. If a document is created with Word or Excel, and
they try to save it to their S drive, all they end up with, is a Zero byte
filename (with date). If they save the file to the C (local) drive, it saves
correctly. They can THEN save the file to the S drive. They have access AND
rights to the S drive. But, Office 2007, as of 3 weeks ago, doesn't like
saving to a Network drive.
Is there a Microsoft patch that should be uninstalled?

"MRand" wrote:

I have a few people, who when trying to save an attachment, get a message
"Cannot save the attachment." This extends over different files (doc, xls,
pdf). There ends up a Zero byte file, where they were trying to save.
I tested to see if it was something like the Outlook Temporary folder
problem - When a file is opened 99 times, in Outlook, the file can no longer
be saved, until you find the Hidden OLKxxxx (or similar) file, that you had
to go to Regedit to find.
I removed ALL files from this folder. But, problem still there. People using
Ms-Office 2007 Professional, with Windows XP (not sure if Sp2 or Sp3).
They have been having this problem for a week. They originally were
wondering if it had anything to do with the bad McAfee definition update.
Thanks for any help.