Outlook and VBA

[Ruegen]

Trying to find the code that will allow me to review and edit an email just before sending it off?

e.g.

''.cc = ""
''.bcc = ""
.Subject = emsubject & " " & emailofsc
.HTMLBody = messagebodyHTML
.somethingherethatwillletmedothat
.DeleteAfterSubmit = False 'This would let Outlook send the note without storing it in your sent bin
.ReadReceiptRequested = True



Also where would I find them in the future...

[June7]

.Visible

will reveal the message object and then you click Send or cancel the message

Messages should be saved in Outlook Sent folder.

[Ruegen]

.Visible

will reveal the message object and then you click Send or cancel the message

Messages should be saved in Outlook Sent folder.

I take it I should remove .send as well?

[June7]

Yes, if you want to review the message first.

[Ruegen]

Yes, if you want to review the message first.

I have

Dim appOutLook As Outlook.Application
Dim MailOutLook As Outlook.MailItem


Set appOutLook = CreateObject("Outlook.Application")
Set MailOutLook = appOutLook.CreateItem(olMailItem)
'open Outlook, attach zip folder or file, send e-mail
With MailOutLook
.BodyFormat = olFormatHTML
.To = "ruegen@domain.com.au"
''.cc = ""
''.bcc = ""
.Subject = emsubject & " " & emailofsc
.HTMLBody = messagebodyHTML
.DeleteAfterSubmit = False 'This would let Outlook send the note without storing it in your sent bin
.ReadReceiptRequested = True
.Visible = True

End With

and I get no compose window to pop up

[Ruegen]

I used

.Display

and it works

[June7]

Sorry, I was trying to pull from memory and apparently crossed wires.

[Ruegen]

Sorry, I was trying to pull from memory and apparently crossed wires.

Thats ok, having .visible helped me find .display - only thing I can see now is if the email is cancelled from sending I would like to perform an action - is that possible using outlook ?

[Ruegen]

say if a person cancels/closes the compose window instead of clicking send...

also .display(modal) doesn't lock up access

[Ruegen]

Sorry - needed to revive this one...\

this might include .close for the mailitem but I don't know how to work this in access.

[ItsMe]

Put an error trap and then exit sub or On Error Resume next just before the .display if display is the last line in the sub

[Ruegen]

Put an error trap and then exit sub or On Error Resume next just before the .display if display is the last line in the sub

Problem is it doesn't cause an error - not using runtime.

[ItsMe]

Problem is it doesn't cause an error - not using runtime.

That does not make sense to me. If there is an error in an accdb file and you are using a full version of Access the debugger prompt will pop up. Runtime does not have a debugger. So, no prompt with RT. It is still an error that needs to be trapped or addressed somehow. This is the purpose of the full version of Access and the debugger. The full version allows you to troubleshoot and address any errors that may occur.

[Ruegen]

That does not make sense to me. If there is an error in an accdb file and you are using a full version of Access the debugger prompt will pop up. Runtime does not have a debugger. So, no prompt with RT. It is still an error that needs to be trapped or addressed somehow. This is the purpose of the full version of Access and the debugger. The full version allows you to troubleshoot and address any errors that may occur.

I get no error when simply closing the compose window so I get no action with using a error trap .

[ItsMe]

Then it is not a problem that needs to be addressed. You are creating an object. As long as the sub routine can finish what it needs to do, there won't be a problem. If you had additional lines that said to have the object open and then come minimize and then change color and then maximize, etc - the user would have an opportunity to interrupt the code from executing.

This is why the DoCmd Sendobject can fail to fully execute. It is committed to sending the object.