Categories in emails
- Thread starter Dan25e
- Start date
Users are often swamped with emails during the normal working day and as such have requested that emails sent from the database either have the email subject as a coloured font as seen in Outlook or better still a category be assigned.
I am not after personal control over anyone's inbox but the process I have replicated and embodied into a database format needs to be as distinct as the old paper based process, one aspect of which is instead of an A4 yellow piece of paper in an in-tray a yellow coloured category in an inbox.
I am not after personal control over anyone's inbox but the process I have replicated and embodied into a database format needs to be as distinct as the old paper based process, one aspect of which is instead of an A4 yellow piece of paper in an in-tray a yellow coloured category in an inbox.
Actually I googled about and found this
https://msdn.microsoft.com/en-us/library/office/aa220082(v=office.11).aspx
From which I extracted this...
Private Sub...()
Dim olApp As Outlook.Application
Dim objMail As Outlook.MailItem
Set olApp = Outlook.Application
With objMail
.To = [a control]
.BCC = "email address"
.Importance = olImportanceHigh
.Subject = "This is a " & Me.Control & " Test Notification "
.BodyFormat = olFormatRichText
.Body = "This is a " & Me.Control & " Test Notification "
.Categories = "Test"
.Display
End With
Popped in amongst the rest of the code for an OnClick event. Works a treat!
https://msdn.microsoft.com/en-us/library/office/aa220082(v=office.11).aspx
From which I extracted this...
Private Sub...()
Dim olApp As Outlook.Application
Dim objMail As Outlook.MailItem
Set olApp = Outlook.Application
With objMail
.To = [a control]
.BCC = "email address"
.Importance = olImportanceHigh
.Subject = "This is a " & Me.Control & " Test Notification "
.BodyFormat = olFormatRichText
.Body = "This is a " & Me.Control & " Test Notification "
.Categories = "Test"
.Display
End With
Popped in amongst the rest of the code for an OnClick event. Works a treat!
Except it doesn't!
The old method I used to send emails was the DoCmd.SendObject method and the database would 'wait' until the email was sent before running the next piece of code. In most cases it was a DoCmd.SaveRecord (important for some auditing code I have running) and then set a value or two in other controls. If I chose not to send the email, the database would do nothing which is what I want it to do.
Using the new method the database reports that the save record function 'isn't available now' and whether I send the email or not it executes the rest of the code.
Do I need to make this method into a separate module and 'call' it? And how would I get it to behave the same way as the DoCmd.SendObject method?
The old method I used to send emails was the DoCmd.SendObject method and the database would 'wait' until the email was sent before running the next piece of code. In most cases it was a DoCmd.SaveRecord (important for some auditing code I have running) and then set a value or two in other controls. If I chose not to send the email, the database would do nothing which is what I want it to do.
Using the new method the database reports that the save record function 'isn't available now' and whether I send the email or not it executes the rest of the code.
Do I need to make this method into a separate module and 'call' it? And how would I get it to behave the same way as the DoCmd.SendObject method?
