SendObject for email references needed
- Thread starter vmon
- Start date
Help does not tell me which references are reuqired. I have 2 CDO references 1.21 and Windows 2000. I am not sure if I need any others and I don't know the difference between the 2 CDO references.
Right now I don't have any CDO references and when I use: DoCmd.SendObject acSendReport, PrmRptName.Value, rst.Fields("Method_Dist"), EmailAddress, , , _
rst.Fields("Email_Subject"), rst.Fields("Email_Text"), True
Nothing happens.
vmon
Right now I don't have any CDO references and when I use: DoCmd.SendObject acSendReport, PrmRptName.Value, rst.Fields("Method_Dist"), EmailAddress, , , _
rst.Fields("Email_Subject"), rst.Fields("Email_Text"), True
Nothing happens.
vmon
pdx_man
Just trying to help
- Local time
- Today, 10:52
- Joined
- Jan 23, 2001
- Messages
- 1,347
From Access Help:
SendObject Action
If you have an electronic mail application that uses the Vendor Independent Mail (VIM) protocol and have installed and set up the dynamic-link library (Mapivim.dll) that converts MAPI mail messages to the VIM protocol, you can send Microsoft Access objects to the VIM mail application.
Otherwise it is in the Microsoft Access 8 Object Library, which should already be selected when looking at your References in a code module.
Is this true for you? Are you using VIM or MAPI? Have you tried just a test trial of SendObject where you specify the values rather than have them dependent on the recordset? Make sure you can send a dummy one first. Your problem may lie elsewhere.
SendObject Action
If you have an electronic mail application that uses the Vendor Independent Mail (VIM) protocol and have installed and set up the dynamic-link library (Mapivim.dll) that converts MAPI mail messages to the VIM protocol, you can send Microsoft Access objects to the VIM mail application.
Otherwise it is in the Microsoft Access 8 Object Library, which should already be selected when looking at your References in a code module.
Is this true for you? Are you using VIM or MAPI? Have you tried just a test trial of SendObject where you specify the values rather than have them dependent on the recordset? Make sure you can send a dummy one first. Your problem may lie elsewhere.
Last edited:
Figured it out. There is a bug in A2K with SendObject not working. Microsoft Knowledge Base Article - 260819 ACC2000: SendObject Method Fails in Access 2000.
I had to add a class object and reference CDO 1.21 to get around problem. I debug it was skipping right over my SendObject.
I had to add a class object and reference CDO 1.21 to get around problem. I debug it was skipping right over my SendObject.
