Because some of the staff are using Runtime they don't have Outlook.
They get errors when loading the access file because they don't have the outlook object library.
Is there a way around this? I'm guessing you can't install it (just the library)?
Because some of the staff are using Runtime they don't have Outlook.
They get errors when loading the access file because they don't have the outlook object library.
Is there a way around this? I'm guessing you can't install it (just the library)?
AFAIK you need the app installed to create the Outlook Object. You could use the CDO option
damn was hoping there was outlook runtime... CDO - will have to research
To which part are you referring to in this link?
I'm reading other places that CDO won't work with 2010 or Outlook 2010? I'm not sure what that is about...
There's a script on CDO half way down
I referred you to a link a few days ago in your attachments thread. To add an attachment within CDO schemas you would use
.AddAttachment strDirectory
where strDirectory = the file path
I'm confused though.
What is CDO?
Will it work with the users using outlook?
Does it do read receipts?
Do you see what's in your sent?
Will it work with Office 2010?
You use the interweb to access schemas that microsoft hosts. There is no need to have any special software installed on the client. You create an that references the CDO schemas. Did you try the example in the link? It is pretty easy. Try this example I posted. Start with a blank DB and follow the instructions in post #7
https://www.accessforums.net/access/...ess-38401.html
This does not depend on Outlook so there is no record of it being in the outbox. If you use a MAPI relay you should be able to have some sort of record. These schemas use SMTP. So I do not believe there will be any usable records of the transaction. I belive there are ways to have CDO dll's on your machine locally and use MAPI. I do not know how to do this though.
It works (and extremely quickly) however, how do I know or see what is sent?You use the interweb to access schemas that microsoft hosts. There is no need to have any special software installed on the client. You create an that references the CDO schemas. Did you try the example in the link? It is pretty easy. Try this example I posted. Start with a blank DB and follow the instructions in post #7
https://www.accessforums.net/access/...ess-38401.html
This does not depend on Outlook so there is no record of it being in the outbox. If you use a MAPI relay you should be able to have some sort of record. These schemas use SMTP. So I do not believe there will be any usable records of the transaction. I belive there are ways to have CDO dll's on your machine locally and use MAPI. I do not know how to do this though.
Do I save them as a record in a new table just to keep track of what emails I have sent??
There are error codes if a communication to the server fails. After the communication is complete, CDO is done. You can build some error trapping and log events in a table, yes. Not sure what the error codes are but you could google them if you want to know what happened.
For the end user because they are used to checking their sent box in their email client to see if emails are sent (and using outlook/docmd.sendobject vba works for this) however this won't pass on that information so how can I make that possible?
It's not a confirmation server wise but a record to the user to see what has just been sent (I do have alerts to say all emails sent however I just get this impression that unless they get a visual guide they will never know if it was successfully sent or not on their end).
You could Bcc the User in the email.
I do this for automation sometimes but reverse. Have the To address be a Do Not Reply Email address I can monitor and then Bcc everyone else.
I believe it would be as easy as adding .Bcc MyEmail@Domain.com
Yup, was anticipating that would be the answerYou could Bcc the User in the email.
I do this for automation sometimes but reverse. Have the To address be a Do Not Reply Email address I can monitor and then Bcc everyone else.
I believe it would be as easy as adding .Bcc MyEmail@Domain.com
What about read receipts? Possible? That's about the only other thing I can think of we require...
(ps as always very grateful for everyone's help here)