// Limit the amount of data to 32Kb. If someone drops a huge amount on data on
// us (e.g. the AsyncTransferSource demo which transfers 10Mb of data) we need
// to limit how much data we try to stuff into the poor memo field. Otherwise
// we could wait for hours before transfer was finished.
MemoContents.Lines.Text := Copy(FTargetDataFormat.Contents, 1, 1024*32);

The VirtualFileStream demo, again by design, limits the amount of data it saves to 1K. This isn't explicitly documented in the source, but the source comments does hint that for a real application you will need to implement your own storage of the data:

// In a real-world application we would write the buffer to disk
// now. E.g.:
//   FileStream.WriteBuffer(p^, BufferSize-Chunk);

If you set a break-point in the OnDrop event handlers it should be pretty clear what is going on with the data.

I will try to work a little on the VirtualFileStream example to make it more obvious what one has to do.

Instead of trying to construct a MSG file from the IMessage interface, which apparently is a really complex and fragile task even though it should be simple, I now keep a reference to the original IStorage interface and save that instead.

I will release the updated demo once I have tidied up the modified source, but I'm out of time for today.

Thanks for the feedback.

I have a little question: If i drag&drop a mail with attachment and "save it", i get an error in the "Outlook drop target demo" : Project OutlookDemo.exe raised exception class EOleSysError with message "access denied ". process stopped….

Mails with no attachments are working fine.

Office Outlook 2003(11.8217.8221) SP3
Borland Delphi Enterprise Version 7.0
Windows XP SP3

Thanx for your great work.

best regards

Erich

This should not be a problem for older versions of Delphi (i.e. pre-D2009) as they will implicitly convert the Unicode strings to Ansi as needed.

E.g. this works just fine:

var
  Filename: string;
begin
  Filename := DropFileTarget1.Files[0];
  ShowMessage(Filename);
end;