DataBase - Rather use Outlook Express than Outlook?? (sometimes)
Asked By Elmtree via AccessMonster.com
16-Jan-10 05:25 PM
Is ther anyway to specify to use Outlook Express rather than Outlook when
emailing thru Access?
--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-setupconfig/201001/1
Outlook
(1)
VBA
(1)
GroupWise
(1)
UrlEscape
(1)
Petersons
(1)
Lotus
(1)
Cf0ab3b7e4f78232
(1)
Setupconfig
(1)
Tony Toews [MVP] replied to Elmtree via AccessMonster.com
Not really. (I have just spent the last several weeks working on
various email options in the Auto FE Updater so I have thorough
knowledge of how the registry and such is working. <smile>)
Now if Outlook Express is the default email client then using the
sendto protocol will work very well and invoke the default email
client.
However chances are very good that if Outlook is installed it is
indeed the default email handler. There is no way, to my knowledge,
to explicitly tell OE to start up and handle the email.
There is automation VBA code which can do this for Outlook, GroupWise
and Lotus Notes explicitly whether they are the default email client
handler or not. it is quite possible that other email clients can be
worked via Automation. But not OE.
Hmm, now that I think about it what you could do is read the default
email client in the registry HKLM\SOFTWARE\Clients\Mail, change it to
Outlook Express, use the sendto protocol to send your email and then
change it back. This all assumes your user has also configured
Outlook Express with their email account settings of course.
See the posting at
http://groups.google.ca/group/microsoft.public.vb.winapi/browse_frm/thread/cf0ab3b7e4f78232/8542dd95bb6db4cd
for sample code on using the sendto method as well as Karl Petersons
reply to my reply to the above posting where he mentions the UrlEscape
code.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
Tony Toews [MVP] replied to Elmtree via AccessMonster.com
BTW why would you want to do this?
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
Granite Fleet Manager http://www.granitefleet.com/
Access Discussions Windows SharePoint Services (1) SQL Server (1) Access 2.0 (1) SharePoint (1) Outlook 2007 (1) Access 2010 (1) Access 2003 (1) Outlook (1) I should note that I am using the data macro to call a VBA function (by setting a local macro variable to the result of the function call). So this is not for the web, I did not see a problem with calling a VBA function (and various places I have seen online mentioned workarounds for calling VBA from a data macro). But, again, while it works when I insert a record in note? In it I added that I was using the AfterInsert macro to run some VBA code (by setting a local variable to the result of a function call). Maybe that maybe that is the problem Yes, in this case, you need a copy of the VBA in the front end. (for testing you can place it in both - since if you happen to open the back end table directly, then the VBA code is ALSO required since the front end might not even be open and the
environment. The class module for one of the forms sends an e-mail using the Outlook object model, (code below). My code runs fine for both Outlook and Outlook Express while in a 2003 runtime environment, but in the 2007 runtime environment I get might be a reference library issue, but see that I had long since referenced: Microsoft Outlook 12.0 Object Library (Actually, in the 2003 environment the reference shows as 11.0 As String, _ DisplayMsg As Boolean, Optional AttachmentPath1, Optional AttachmentPath2, Optional AttachmentPath3) Dim objOutlook As Outlook.Application Dim objOutlookMsg As Outlook.MailItem Dim objOutlookRecip As Outlook.Recipient Dim objOutlookAttach As Outlook.Attachment ' Create the Outlook session. Set objOutlook = CreateObject("Outlook.Application") ' Create the message. Set objOutlookMsg
Groupwise to Outlook DataBase In AccessXP I use the following vba code to email a message thru GroupWise, the company I work for is changing to Outlook and I need to re-write this vba code for Outlook. I got most of it but I am stuck on getting Outlook to open and log in the current user which Groupwise did with the line - Set
Docmd.SendObject and Outlook DataBase HI All, My company is switching from Groupwise to Outlook 2007 and so I need to change / test all my applications that have email functionality using Groupwise. In my testing to date I have an issue with Docmd.Sendobject. with Groupwise the Docmd.Sendobject would send the email right away whether or not Groupwise was open as an example; DoCmd.SendObject acSendNoObject, , , "bobh@company.com", , , "DoCmd test", "Testing", False the above would send the email reguardless of the state of Groupwise (opened or closed) with Outlook the Docmd.Sendobject, if Outlook is closed the email will be placed in Outlook's
all previous versions of MS Access prior to Access 2007 to export a contact to Outlook. It worked exporting from Access 2003 / 2002 / 2000 to Outlook including Outlook 2007. It worked whether or not Outlook was open. However, now with Access 2007 it only works if Outlook is closed. Dim objOutlook As Object Dim objOutlookApp As Object Set objOutlook = CreateObject("Outlook.Application") Set objOutlookApp = objOutlook.CreateItem(2) With objOutlookApp .FirstName = "John" .LastName = "Smith" ' . . . .Save End With So I modified the code to determine if Outlook is running, however I get an error message if Outlook is running: If fIsAppRunning("Outlook") = True Then ' (Outlook is running) Set objOutlook = GetObject(, "Outlook.Application