I've done this before in a previous db that I developed.
Two ways you can do it. I found a db at blueclaw that allows you to create a form and type in the email address if known which sends it directly from MS Access and does NOT even open Outlook. You can then just add an email listing to a contacts table, or create a contacts table and have one in there allowing people to select the email or person from the list. **The DB is attached**
Coding that I have in another email demo that I have is below, which is in a module...
Code:
Function E_MailOutLook()
Dim oOutlook As Outlook.Application
Dim oMessage As Outlook.MailItem
' Prepare Outlook
Set oOutlook = CreateObject("Outlook.Application")
Set oMessage = oOutlook.CreateItem(olMailItem)
' Move data to Outlook defined variables
With oMessage
.Importance = olImportanceHigh 'High importance
.To = "EMAIL ADDRESS GOES HERE"
.CC = "CC EMAIL ADDRESS GOES HERE"
.BCC = "BCC EMAIL ADDRESS GOES HERE"
.Subject = "YOUR SUBJECT GOES HERE"
.Body = "YOUR_E-MAIL_MESSAGE_GOES_HERE"
' If you want attachments use the following line
.Attachments.Add "YOUR FILES PATH AND NAME", , , "YOUR FILES NAME"
' If you want the screen to be seen then add the following line
.Display
.Send
End With
' Clear Set Items
Set oOutlook = Nothing
Set oMessage = Nothing
End Function
I'll see if I can find the other coding / db examples to eliminate the message you're getting because I know I have it somewhere, someplace.
I've done this before in a previous db that I developed.
Two ways you can do it. I found a db at blueclaw that allows you to create a form and type in the email address if known which sends it directly from MS Access and does NOT even open Outlook. You can then just add an email listing to a contacts table, or create a contacts table and have one in there allowing people to select the email or person from the list. **The DB is attached**
Coding that I have in another email demo that I have is below, which is in a module...
Code:
Function E_MailOutLook()
Dim oOutlook As Outlook.Application
Dim oMessage As Outlook.MailItem
' Prepare Outlook
Set oOutlook = CreateObject("Outlook.Application")
Set oMessage = oOutlook.CreateItem(olMailItem)
' Move data to Outlook defined variables
With oMessage
.Importance = olImportanceHigh 'High importance
.To = "EMAIL ADDRESS GOES HERE"
.CC = "CC EMAIL ADDRESS GOES HERE"
.BCC = "BCC EMAIL ADDRESS GOES HERE"
.Subject = "YOUR SUBJECT GOES HERE"
.Body = "YOUR_E-MAIL_MESSAGE_GOES_HERE"
' If you want attachments use the following line
.Attachments.Add "YOUR FILES PATH AND NAME", , , "YOUR FILES NAME"
' If you want the screen to be seen then add the following line
.Display
.Send
End With
' Clear Set Items
Set oOutlook = Nothing
Set oMessage = Nothing
End Function
I'll see if I can find the other coding / db examples to eliminate the message you're getting because I know I have it somewhere, someplace.
thanks for the response but my email is being mailed through Macros to send a massive amount of reports.. I think I should've clarified that in the original post, sorry.
Ahh....well bmail is a great little command line tool for emailing without much hassle. Works great for simpler stuff like sending logs or error alerts.
They should still be able to implement other controls and constraints for emails coming from outside sources and whatnot. This should only affect internal messaging.
Your network admin should have other controls and constraints to prohibit the security in Outlook from being lowered to a dangerous level. Doing the above post should only lower the security for internal emails and not the entire system. They can disable HTML formatted emails from coming through so that ALL emails are seen as plain-text, they can strip or scan attachments from incoming emails, and many other security measures can be implemented to help combat any issues that may arise from doing what is said in that link.
