Macro to delete email as per string or cell data
Good Morning
Is there a way to have an excel macro delete an email/s from a particular sender, I know you can use this in outlook but I need it to be done via excel if possible.
I have tried lots of variants I have seen online but none of them work.
I'm using excel & outlook 2010
Thanks Dave
If it can be done in Outlook (and it can) then it's a simple matter to do it in Excel. You just need to create/set a reference to Outlook in the code and then a few minor changes.
As you 'have tried lots of variants' then post one or 2 of the samples you did try. There's no need to start afresh when there's existing code.
Hi Cytop
here's what I tried
Please Login or Register to view this content.
also having the option to delete email as per subject would be great
First question is are you going to use Early Binding or Late Binding?
If you don't know what these are then you really should go search "early late binding vba" and read, then decide which to use...
Also, the SenderName may not contain a full email address, but a 'friendly' name, if available and there usually is one. Would it be an idea to check the actual Sender email address?
Last obvious things:
There's an error on the line
Easy enough to spot once you know it's there but you should consider using the 'Option Explicit' compiler directive to catch that when the code is compiled.Please Login or Register to view this content.
You might like to use the 'Option Compare Text' compiler directive to remove the need to convert text to upper/lower case when comparing.
Hi Cytop
Right I believe Early Binding is whats needed, are you able to provide the appropriate code to achieve the above if at all possible, with subject search as well maybe.
no worries if not but it would be a big help :-)
I would prefer you understand the implications of using Early Binding but it is simply a matter of adding a reference to the Outlook using the Tools/References menu and change the CreateObject line to
The Subject search can wait until this is working...Please Login or Register to view this content.
Hi Ctop
Maybe my original
Last edited by dave1983; 01-24-2017 at 10:25 AM.
Hi Ctop
maybe my original understanding was flawed Ill look at some more articles, can I check then that the suggestion you made only needs to be done within excel as I realise I missed a vital bit of information stating that the other macro I have sends an email to a recipient with an attachment, saves it and at that point I then want a macro to delete the email in the other persons inbox as a separate email will be sent of smaller size.
I basically want the email that was sent with the attachment deleted so it doesn't clog there inbox up.
Last edited by dave1983; 01-24-2017 at 10:28 AM.
Just in case its useful for others on this subject this really helps
http://excelmatters.com/2013/09/23/v...-late-binding/
Ctop I know see that Late binding helps deal with issues around version of program etc.
Hi dave1983,
It's not a question of Early vs Late Binding. My personal preference is late binding which doesn't require a library reference, and is independent of Office Version. However, if any references are made to Outlook Enumerated constants their values have to be explicitly declared.
Enumerated Constant Reference:
https://msdn.microsoft.com/en-us/lib...ffice.11).aspx
For more information on Early vs Late Binding see:
http://peltiertech.com/Excel/EarlyLateBinding.html
http://excelmatters.com/2013/09/23/v...-late-binding/
a. You seemed to be using the 'Inbox ' for folder 'Outlook Data Folder' instead of the 'Inbox' for the Default User Name (Account 1).
b. In addition, you should consider using 'Option Explicit' to avoid typos from ruining your day.
c. Try to avoid using 'On Error Resume Next'. It often masks real problems.
It is a best practice to declare all variables. If you misspell a variable in your code, VBA will silently assume it is a Variant variable and go on executing with no clue to you that you have a bug. Go to the VBA development window, click Tools, Options, and check "Require Variable Declaration." This will insert the following line at the top of all new modules:
This option requires all variables to be declared and will give a compiler error for undeclared variables.Please Login or Register to view this content.
Try:
The following debugging information may help you now and in the future:Please Login or Register to view this content.
Debugger Secrets:
a. Press 'F8' to single step (goes into subroutines and functions).
b. Press SHIFT 'F8' to single step OVER subroutines and functions.
c. Press CTRL 'F8' to stop at the line where the cursor is.
d. 'Left Click' the margin to the left of a line to set (or clear) a BREAKPOINT.
e. Press CTRL 'G' to open the IMMEDIATE WINDOW. 'debug.print' statements send their
output to the IMMEDIATE WINDOW.
f. Select View > Locals to see all variables while debugging.
g. To automatically set a BREAKPOINT at a certain location put in the line:
'Debug.Assert False'
h. To conditionally set a BREAKPOINT at a certain location put in lines similar to:
if i >= 20 and xTV20 > 99.56 then
Debug.Assert False
endif
i. A variable value will be displayed by putting the cursor over the variable name.
To manually set a breakpoint, see http://www.wiseowl.co.uk/blog/s196/breakpoints.htm
Lewis
Last edited by LJMetzger; 01-24-2017 at 12:12 PM.
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
LinkBack URL
About LinkBacks
Register To Reply
Bookmarks