Actually Send Message - Without Opening Msg for edit

  • Thread starter Thread starter Charlie via AccessMonster.com
  • Start date Start date
C

Charlie via AccessMonster.com

How do I actually send a message? I have the code below to send email, but
all it does is open Outlook with the To: field populated. Then the user
has to click the send button.

How do I just send the message without opening Outlook for edit?

Here's my code:

Private Sub ComboStatus_AfterUpdate()
If Me.ComboStatus = "closed" Then
If MsgBox("Only Person Reported This Issue Can Close It. Do you wish to
Continue? ", vbOKCancel) <> vbOK Then

Else
Me.CloseDate = Date
MsgBox "Person Reported this Issue Is Notified!"
DoCmd.SendObject acSendNoObject, , , Me.ReportedbyEmail, , , "Discrepancy
Issue Tracking No: " & Me.TrackingNo & "", "THIS ISSUE HAS BEEN CLOSED.
Please Confirm Closure or Reopen. THANK YOU! - Closed Date: " & Date

Exit Sub
End If
End If

End Sub
 
Charlie said:
How do I actually send a message? I have the code below to send
email, but all it does is open Outlook with the To: field populated.
Then the user has to click the send button.

How do I just send the message without opening Outlook for edit?

The ninth (optional) argument for SendObject is a True/False entry that
determines whether the user gets to edit the message or whether it is sent
immediately. It defaults to True so all you have to do is supply a False
for that argument.
 
Hi Rick,

I tried that but I guess Outlook tries to send, but still prompts are you
sure you want to send this email. It gives the person the option to "click
No". With this a person can still close an issue and no one gets notified.

Is there an override the Outlook prompt for this??

Thanks,
Charlie
 
Charlie via AccessMonster.com said:
Hi Rick,

I tried that but I guess Outlook tries to send, but still prompts are you
sure you want to send this email. It gives the person the option to "click
No". With this a person can still close an issue and no one gets notified.

Is there an override the Outlook prompt for this??

That is the new Outlook security feature and No, it cannot be circumvented
except to send your message without using Outlook.
 
Rick Brandt said:
That is the new Outlook security feature and No, it cannot be
circumvented except to send your message without using Outlook.

Actually, I believe the Redemption library, a third-party product, is
designed to get around this problem.
 
Dirk Goldgar said:
Actually, I believe the Redemption library, a third-party product, is
designed to get around this problem.

Yes, but it does so by providing its own object model over extended MAPI that
mimics the one in Outlook so in affect when you use Redemption you are no longer
automating Outlook.
 
Rick Brandt said:
Yes, but it does so by providing its own object model over extended
MAPI that mimics the one in Outlook so in affect when you use
Redemption you are no longer automating Outlook.

True, o King. But from the OP's point of view, that may be good enough.
 
Dirk said:
True, o King. But from the OP's point of view, that may be good
enough.


Actually, at our company the more common annoying security popup is this one...

"A program is trying to access the Global Address Book. Do you want to allow
this?"

In my testing the use of Redemption does not prevent this one.
 
Rick Brandt said:
Actually, at our company the more common annoying security popup is
this one...

"A program is trying to access the Global Address Book. Do you want
to allow this?"

In my testing the use of Redemption does not prevent this one.

I take it both of you have looked into ClickYes?

http://www.contextmagic.com/express-clickyes/

I've used it and it works a treat.

RuralGuy
 
RuralGuy said:
I take it both of you have looked into ClickYes?

http://www.contextmagic.com/express-clickyes/

I've used it and it works a treat.

I'm aware of it, though I've never had occasion to use it. I'm not
awfully fond of having an application constantly running in the
background watching for confirmnation dialogs to appear; I'd rather
program so that the dialogs are never triggered in the first place --
when I can. But that's the only thing I have against ClickYes. I've
heard it recommended many times.
 
Dirk said:
I'v never had to deal with that. Does this help?

http://support.microsoft.com/?kbid=329765

I believe that's a slightly different message then the one I am talking
about. The message I am talking about started appearing on our corporate
machines after some some sort of Windows or Office update was "pushed" onto
machines using group policies and it later appeared on all new PCs that had
Outlook 2003 on them. In my case Outlook is definitely running when the
message is displayed.
 
Back
Top