>>
But I have in the past I have received workbooks from clients, where Excel
will not open the attachment.
>>
I have as well. But that doesn't mean it's because Excel was open or that OE
sent the file off the disk, assuming the sender used OE.
>>
I know that those clients keep the large workbooks open on their desktop
continually throughout the day, and when they alter something they didn't mean
to, or shouldn't - and the stuff in them is no longer presented as they want,
or doesn't
balance: Then they ship the thing to me to have it 'put right' and returned.
<snip>
Having tried the removed file and pulled cable - then the only other things
are:
A large complex file - kept open and being changed (saved) during the
attach,
and on through the transmit -
and that will be fun to get timed right on a fast comms connection.
And the effect of AV processing on outward bound mail
- especially if it's set to remove the virus, and allow processing to
continue with the 'cleaned file'
Also - I suppose we shouldn't discount basic transmission errors -
>>
Any file can become corrupt when sent - usually it's because something screwed
up during transmission and the file ended up munged. Two causes I am aware of
are virus scanning and loss of TNEF data (affects mail sent using Outlook only).
If a program has a lock on a file it's more likely the email client will be
unable to send it and display an alert, rather than send a corrupt copy. A few
programs might hook into the document on the hard drive and attach it went sent
from the client - but OE is not one of them. (Pegasus and Eudora would be more
likely to do this since they store attachments in a folder on the drive,
although I don't know that they do. One of the guys who uses those programs
would.)
--
----------------------------------------
WIN-HOME Archives: http://PEACH.EASE.LSOFT.COM/archives/WIN-HOME.html
Contact the List Owner about anything: [EMAIL PROTECTED]
Official Win-Home List Members Profiles Page
http://www.besteffort.com/winhome/Profiles.html
