>You're lucky to catch me (I've not been online for a while).

:)

>MAPI will work with a range of different clients. And, no you won't be able to delete mail using the MAPI control.

I guessed this might be the case:(

Folks without Outlook will just have to do their own deletions.

Hmm looks like I should use the Mapi class for all transfers but then check if they have Outlook. If they do I can use the Outlook class to move the mail to the deleted folder. Filtering on subject works just fine so I can delete anything with a particular subject set by my app.


Thanks for your help Nigel

I have marked the thread as solved:)



>
>>Some of this might seem a bit obvious but I have to ask it to be on the safe side.
>>
>>I am hoping to use one of Nigel Coates mail classes in an application that transfers Zipped DBFs as attachments.
>>
>>The idea behind the application is the my app will pass these DBFs back and forth using the mail without any involvement in the process required by the user.
>>
>>The Outlook class is his latest and presumably has more functionality so it would be nice to use it.
>>
>>However I can not be sure that all my clients will have MS Outlook and I guess this is a requirement for the Outlook class to function.
>>
>>Am I correct in thinking that his MAPI class will work with a wider variety of mail clients ie any that are MAPI complient and so it will also work with Outlook Express.
>>
>>I am also hoping to delete items of mail after my app has dealt with the attachments, will this be possible with the MAPI class.
>>
>>I have had trouble getting the filter for SENDERNAME working with the Outlook class, there seems to be no filter conditions being set for this parameter so setting it has no effect. Has anyone else noticed this or am I missing something obvious.
>>
>>
>>All help and observations greatfully received