Closed
Bug 323332
Opened 20 years ago
Closed 17 years ago
Send attachments w/MSAccess SendObject via MAPI - wrong file attached under error condition.
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: KingRonPoindexter, Unassigned)
Details
(Whiteboard: closeme 2008-09-04)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Have application created in AccessXP VBA which sends class rosters to faculty members as attached .rtf files. Works fine using Outlook Express as default MAPI client. Today job was run by user with Thunderbird set as default MAPI client. Thunderbird worked fine under non-error conditions and performed MUCH faster than OE. However upon error (bad email address) Thunderbird performed erratically.
1) A few of the 300+ email addresses are bad and the email server throws the appropriate error on processing the bad address.
2) Thunderbird pops up error notification dialog OK'd by user.
3) Thunderbird continues processing with the next email address in the queue; however, it attaches the .rtf file for the 'previous' (bad-address) record to the 'current' record rather than discarding the 'previous' attachment as well as the bad email address.
4) The processing continues, but now each email sent contains the attachment meant for the previous record. Any subsequent errors have the same result so that by the end of the process, the file attached is off by the number of times the bad address error was thrown.
5) Outlook Express apparently handles this error condition differently, as the bad-email attachments are skipped over and the email queue and attacment queue remain in sync.
Reproducible: Always
Steps to Reproduce:
1. MSAccess SendObject report as .rtf attachment in program loop with Thunderbird as default email client.
2. Invalid email address in To: field
3. Close Thunderbird error dialog when notifed of invalid email address by smtp server.
Actual Results:
.RTF file attached to email is off by (number of email errors)
Expected Results:
Attachment specified in the 'SendObject' should be attached to the 'current' email regardless of the number of previous bad address record errors handled.
For what it's worth here's the MSAccess VBA subroutine that sends the 'ContactRosters' report as an attachment to the faculty member whose record is 'current' in the list of EMail addresses in the query 'uSysFacEMail'. Note that when sent, the email address and attachment are sent as a unit, but after the error as described the two parts are out of sync.
<vba>
Private Sub btnEMail_Click()
Dim rs As Recordset
Dim SQ As String
Dim ESubj As String
Dim EBody As String
Dim ETech As String
Dim EAddr As String
Dim CBody As String
Dim sSafe As String
sSafe = DLookup("[usDebug]", "uSysCtl", "[usID] = 1")
ESubj = DLookup("[usEMailSubj]", "uSysCtl", "[usID] = 1")
EBody = DLookup("[usEMailBody]", "uSysCtl", "[usID] = 1")
ETech = DLookup("[usTechEmail]", "uSysCtl", "[usID] = 1")
Set rs = CurrentDb.OpenRecordset("uSysFacEMail", dbOpenSnapshot)
While Not rs.EOF
SQ = "UPDATE uSysCtl SET uSysCtl.usCurrInst = '" & rs("ID") & "'"
DoCmd.SetWarnings False
DoCmd.RunSQL SQ
DoCmd.SetWarnings True
CBody = "Dear " & rs("FirstName") & ":" & vbCrLf & vbCrLf & EBody
If (sSafe = True) Then
EAddr = ETech
Else
EAddr = rs("EMail")
End If
DoCmd.SendObject acSendReport, "ContactRosters", acFormatRTF, EAddr, , , ESubj & " (" & rs("LastName") & ")", CBody, False
rs.MoveNext
Wend
rs.Close: Set rs = Nothing
End Sub
</vba>
Updated•18 years ago
|
QA Contact: message-compose
Comment 1•17 years ago
|
||
Reporter, does the issue still occur in the latest supported 2.0.0.x / Shredder trunk nightlies?
(1.5.0.x is now end-of-life and the latest supported 2.0.0.x is 2.0.0.16)
Whiteboard: closeme 2008-09-04
Updated•17 years ago
|
Assignee: mscott → nobody
Comment 2•17 years ago
|
||
RESO INCO due to lack of response to last comment. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•