In case anyone has ran into this yet. The following code used to work with
older versions of the MS Outlook library, but would error out in 2007:
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
After doing some testing, I found that the code will work provided that you
first OPEN MS Outlook. In previous versions, you didn't have to have outlook
open, and it would still add the e-mail to the outbox.
If there's a fix to where you wouldn't need to open Outlook, I'd love to
know.
FYI, the error code if you don't first open Outlook is Err = 287. It would
error out upon hitting the .recipients.add statement. With Outlook opened
first, all runs well.
9  2230 
On Mon, 20 Aug 2007 21:30:19 -0500, "ARC" <an**@andyc.comwrote:
But your CreateObject line opens Outlook, so I don't understand.
Just add:
objOutlook.Visible = True
and you can see for yourself.
Sorry I don't have Outlook2007 installed properly here so I cannot
test this further.
What is the Err.Description when you take an error?
-Tom.
>In case anyone has ran into this yet. The following code used to work with
older versions of the MS Outlook library, but would error out in 2007:
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
After doing some testing, I found that the code will work provided that you
first OPEN MS Outlook. In previous versions, you didn't have to have outlook
open, and it would still add the e-mail to the outbox.
If there's a fix to where you wouldn't need to open Outlook, I'd love to
know.
FYI, the error code if you don't first open Outlook is Err = 287. It would
error out upon hitting the .recipients.add statement. With Outlook opened
first, all runs well.
Tom,
As an update to this. Putting the line: ObjOutlook.Visible = true had no
affect.
I believe the change is in the new reference library: MS Outlook 12
As I tested in my Access 97 runtime app, and it still errored out with the
same message. However, if you first open Outlook, then there is no error,
and it works as it should.
Again, in previous versions of the library file, you didn't need to first
open Outlook, and messages would be written to Outlook's outbox. Not so with
v12, but at least it works, and chances are the user will have Outlook open
most of the time.
Andy
"Tom van Stiphout" <no*************@cox.netwrote in message
news:p4********************************@4ax.com...
On Mon, 20 Aug 2007 21:30:19 -0500, "ARC" <an**@andyc.comwrote:
But your CreateObject line opens Outlook, so I don't understand.
Just add:
objOutlook.Visible = True
and you can see for yourself.
Sorry I don't have Outlook2007 installed properly here so I cannot
test this further.
What is the Err.Description when you take an error?
-Tom.
>>In case anyone has ran into this yet. The following code used to work with
older versions of the MS Outlook library, but would error out in 2007:
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
After doing some testing, I found that the code will work provided that
you
first OPEN MS Outlook. In previous versions, you didn't have to have
outlook
open, and it would still add the e-mail to the outbox.
If there's a fix to where you wouldn't need to open Outlook, I'd love to
know.
FYI, the error code if you don't first open Outlook is Err = 287. It would
error out upon hitting the .recipients.add statement. With Outlook opened
first, all runs well.
Oh yes, and I did add error-trapping code for the error number given. If it
hits that, I inform the user that Outlook must be open prior to creating the
e-mail from the Access program.
"Tom van Stiphout" <no*************@cox.netwrote in message
news:p4********************************@4ax.com...
On Mon, 20 Aug 2007 21:30:19 -0500, "ARC" <an**@andyc.comwrote:
But your CreateObject line opens Outlook, so I don't understand.
Just add:
objOutlook.Visible = True
and you can see for yourself.
Sorry I don't have Outlook2007 installed properly here so I cannot
test this further.
What is the Err.Description when you take an error?
-Tom.
>>In case anyone has ran into this yet. The following code used to work with
older versions of the MS Outlook library, but would error out in 2007:
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
After doing some testing, I found that the code will work provided that
you
first OPEN MS Outlook. In previous versions, you didn't have to have
outlook
open, and it would still add the e-mail to the outbox.
If there's a fix to where you wouldn't need to open Outlook, I'd love to
know.
FYI, the error code if you don't first open Outlook is Err = 287. It would
error out upon hitting the .recipients.add statement. With Outlook opened
first, all runs well.
On Aug 20, 10:30 pm, "ARC" <a...@andyc.comwrote:
In case anyone has ran into this yet. The following code used to work with
older versions of the MS Outlook library, but would error out in 2007:
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
After doing some testing, I found that the code will work provided that you
first OPEN MS Outlook. In previous versions, you didn't have to have outlook
open, and it would still add the e-mail to the outbox.
If there's a fix to where you wouldn't need to open Outlook, I'd love to
know.
FYI, the error code if you don't first open Outlook is Err = 287. It would
error out upon hitting the .recipients.add statement. With Outlook opened
first, all runs well.
I know this is a long shot, but your problem may have been caused by
timing issues. Perhaps the new version of Outlook is taking longer to
open. The code, trying to be helpful and efficient, continues on
without waiting for CreateObject to finish and discovers that Outlook
is not open yet. That would explain why it works when Outlook is
already open. BTW, CreateObject seems never to create more than one
instance of Outlook. Try some DoEvent's in a loop (maybe 2000 times)
after your CreateObject call to see if that's the case. It's true
that the 'Set objOutlookMsg = objOutlook.CreateItem(olMailItem)' line
seems like it might require Outlook to be open, but perhaps it
doesn't. You can also combine this with Tom's suggestion by putting
objOutlook.Visible = True right before the DoEvents loop.
James A. Fortune CD********@FortuneJames.com
I'll try that, and report back. I already have some looping code that pauses
a few seconds, I'll insert that and let you know. Outlook 2007 does take
longer to load. When you first launch, there are a few sections that say
"..loading.." , so it could very well be the timing of it all.
I don't know if I can use the ojbOutlook.visible property, as on one screen,
it's a batch e-mail process of invoices to many different customers, etc.
I'll post the results soon..and thanks for the idea!
<CD********@FortuneJames.comwrote in message
news:11**********************@z24g2000prh.googlegr oups.com...
On Aug 20, 10:30 pm, "ARC" <a...@andyc.comwrote:
>In case anyone has ran into this yet. The following code used to work
with
older versions of the MS Outlook library, but would error out in 2007:
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
After doing some testing, I found that the code will work provided that
you
first OPEN MS Outlook. In previous versions, you didn't have to have
outlook
open, and it would still add the e-mail to the outbox.
If there's a fix to where you wouldn't need to open Outlook, I'd love to
know.
FYI, the error code if you don't first open Outlook is Err = 287. It
would
error out upon hitting the .recipients.add statement. With Outlook opened
first, all runs well.
I know this is a long shot, but your problem may have been caused by
timing issues. Perhaps the new version of Outlook is taking longer to
open. The code, trying to be helpful and efficient, continues on
without waiting for CreateObject to finish and discovers that Outlook
is not open yet. That would explain why it works when Outlook is
already open. BTW, CreateObject seems never to create more than one
instance of Outlook. Try some DoEvent's in a loop (maybe 2000 times)
after your CreateObject call to see if that's the case. It's true
that the 'Set objOutlookMsg = objOutlook.CreateItem(olMailItem)' line
seems like it might require Outlook to be open, but perhaps it
doesn't. You can also combine this with Tom's suggestion by putting
objOutlook.Visible = True right before the DoEvents loop.
James A. Fortune
CD********@FortuneJames.com
No luck. I even tried setting the pause loop very high.
I looked into the new settings in Outlook, especially those in the trust
center, and tried a few options dealing with unsigned macros, and
programmatic access, all to no avail.
For now, I'll just trap the error code, and inform the user that they need
to first have Outlook opened. I never noticed a problem in previous versions
of the MS Outlook Libary. Something new in 2007, I suppose.
Thanks again,
Andy
"ARC" <an**@andyc.comwrote in message
news:%p******************@newssvr11.news.prodigy.n et...
I'll try that, and report back. I already have some looping code that
pauses a few seconds, I'll insert that and let you know. Outlook 2007 does
take longer to load. When you first launch, there are a few sections that
say "..loading.." , so it could very well be the timing of it all.
I don't know if I can use the ojbOutlook.visible property, as on one
screen, it's a batch e-mail process of invoices to many different
customers, etc.
I'll post the results soon..and thanks for the idea!
<CD********@FortuneJames.comwrote in message
news:11**********************@z24g2000prh.googlegr oups.com...
>On Aug 20, 10:30 pm, "ARC" <a...@andyc.comwrote:
>>In case anyone has ran into this yet. The following code used to work
with
older versions of the MS Outlook library, but would error out in 2007:
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
After doing some testing, I found that the code will work provided that
you
first OPEN MS Outlook. In previous versions, you didn't have to have
outlook
open, and it would still add the e-mail to the outbox.
If there's a fix to where you wouldn't need to open Outlook, I'd love to
know.
FYI, the error code if you don't first open Outlook is Err = 287. It
would
error out upon hitting the .recipients.add statement. With Outlook
opened
first, all runs well.
I know this is a long shot, but your problem may have been caused by
timing issues. Perhaps the new version of Outlook is taking longer to
open. The code, trying to be helpful and efficient, continues on
without waiting for CreateObject to finish and discovers that Outlook
is not open yet. That would explain why it works when Outlook is
already open. BTW, CreateObject seems never to create more than one
instance of Outlook. Try some DoEvent's in a loop (maybe 2000 times)
after your CreateObject call to see if that's the case. It's true
that the 'Set objOutlookMsg = objOutlook.CreateItem(olMailItem)' line
seems like it might require Outlook to be open, but perhaps it
doesn't. You can also combine this with Tom's suggestion by putting
objOutlook.Visible = True right before the DoEvents loop.
James A. Fortune
CD********@FortuneJames.com
By the way, if you put a break and step through the code, the line below
triggers the On Error (where SendAddr is a string loaded with a valid
e-mail):
Set objOutlookRecip = .Recipients.Add(SendAddr)
"ARC" <an**@andyc.comwrote in message
news:%p******************@newssvr11.news.prodigy.n et...
I'll try that, and report back. I already have some looping code that
pauses a few seconds, I'll insert that and let you know. Outlook 2007 does
take longer to load. When you first launch, there are a few sections that
say "..loading.." , so it could very well be the timing of it all.
I don't know if I can use the ojbOutlook.visible property, as on one
screen, it's a batch e-mail process of invoices to many different
customers, etc.
I'll post the results soon..and thanks for the idea!
<CD********@FortuneJames.comwrote in message
news:11**********************@z24g2000prh.googlegr oups.com...
>On Aug 20, 10:30 pm, "ARC" <a...@andyc.comwrote:
>>In case anyone has ran into this yet. The following code used to work
with
older versions of the MS Outlook library, but would error out in 2007:
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
After doing some testing, I found that the code will work provided that
you
first OPEN MS Outlook. In previous versions, you didn't have to have
outlook
open, and it would still add the e-mail to the outbox.
If there's a fix to where you wouldn't need to open Outlook, I'd love to
know.
FYI, the error code if you don't first open Outlook is Err = 287. It
would
error out upon hitting the .recipients.add statement. With Outlook
opened
first, all runs well.
I know this is a long shot, but your problem may have been caused by
timing issues. Perhaps the new version of Outlook is taking longer to
open. The code, trying to be helpful and efficient, continues on
without waiting for CreateObject to finish and discovers that Outlook
is not open yet. That would explain why it works when Outlook is
already open. BTW, CreateObject seems never to create more than one
instance of Outlook. Try some DoEvent's in a loop (maybe 2000 times)
after your CreateObject call to see if that's the case. It's true
that the 'Set objOutlookMsg = objOutlook.CreateItem(olMailItem)' line
seems like it might require Outlook to be open, but perhaps it
doesn't. You can also combine this with Tom's suggestion by putting
objOutlook.Visible = True right before the DoEvents loop.
James A. Fortune
CD********@FortuneJames.com
ARC wrote:
For now, I'll just trap the error code, and inform the user that they need
to first have Outlook opened. I never noticed a problem in previous versions
of the MS Outlook Libary. Something new in 2007, I suppose.
If you care, that's what I do. I check to see if Outlook is open, I
inform if it's not open and cancel. I don't know which profile is being
used and I don't care. I figure if someone wants to send an email, open
the email program first and select the profile.
>
Thanks again,
Andy
"ARC" <an**@andyc.comwrote in message
news:%p******************@newssvr11.news.prodigy.n et...
>>I'll try that, and report back. I already have some looping code that
pauses a few seconds, I'll insert that and let you know. Outlook 2007 does
take longer to load. When you first launch, there are a few sections that
say "..loading.." , so it could very well be the timing of it all.
I don't know if I can use the ojbOutlook.visible property, as on one
screen, it's a batch e-mail process of invoices to many different
customers, etc.
I'll post the results soon..and thanks for the idea!
<CD********@FortuneJames.comwrote in message
news:11**********************@z24g2000prh.google groups.com...
>>>On Aug 20, 10:30 pm, "ARC" <a...@andyc.comwrote:
In case anyone has ran into this yet. The following code used to work
with
older versions of the MS Outlook library, but would error out in 2007:
Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
After doing some testing, I found that the code will work provided that
you
first OPEN MS Outlook. In previous versions, you didn't have to have
outlook
open, and it would still add the e-mail to the outbox.
If there's a fix to where you wouldn't need to open Outlook, I'd love to
know.
FYI, the error code if you don't first open Outlook is Err = 287. It
would
error out upon hitting the .recipients.add statement. With Outlook
opened
first, all runs well.
I know this is a long shot, but your problem may have been caused by
timing issues. Perhaps the new version of Outlook is taking longer to
open. The code, trying to be helpful and efficient, continues on
without waiting for CreateObject to finish and discovers that Outlook
is not open yet. That would explain why it works when Outlook is
already open. BTW, CreateObject seems never to create more than one
instance of Outlook. Try some DoEvent's in a loop (maybe 2000 times)
after your CreateObject call to see if that's the case. It's true
that the 'Set objOutlookMsg = objOutlook.CreateItem(olMailItem)' line
seems like it might require Outlook to be open, but perhaps it
doesn't. You can also combine this with Tom's suggestion by putting
objOutlook.Visible = True right before the DoEvents loop.
James A. Fortune
CD********@FortuneJames.com
'course I do! And thanks for the reply.
"Salad" <oi*@vinegar.comwrote in message
news:13*************@corp.supernews.com...
ARC wrote:
>For now, I'll just trap the error code, and inform the user that they
need to first have Outlook opened. I never noticed a problem in previous
versions of the MS Outlook Libary. Something new in 2007, I suppose.
If you care, that's what I do. I check to see if Outlook is open, I
inform if it's not open and cancel. I don't know which profile is being
used and I don't care. I figure if someone wants to send an email, open
the email program first and select the profile.
>>
Thanks again,
Andy
"ARC" <an**@andyc.comwrote in message
news:%p******************@newssvr11.news.prodigy. net...
>>>I'll try that, and report back. I already have some looping code that
pauses a few seconds, I'll insert that and let you know. Outlook 2007
does take longer to load. When you first launch, there are a few sections
that say "..loading.." , so it could very well be the timing of it all.
I don't know if I can use the ojbOutlook.visible property, as on one
screen, it's a batch e-mail process of invoices to many different
customers, etc.
I'll post the results soon..and thanks for the idea!
<CD********@FortuneJames.comwrote in message
news:11**********************@z24g2000prh.googl egroups.com...
On Aug 20, 10:30 pm, "ARC" <a...@andyc.comwrote:
>In case anyone has ran into this yet. The following code used to work
>with
>older versions of the MS Outlook library, but would error out in 2007:
>
>Dim objOutlook As Outlook.Application
Dim objOutlookMsg As Outlook.MailItem
Dim objOutlookRecip As Outlook.Recipient
Dim objOutlookAttach As Outlook.Attachment
Set objOutlook = CreateObject("Outlook.Application")
' Create the message.
Set objOutlookMsg = objOutlook.CreateItem(olMailItem)
With objOutlookMsg
Set objOutlookRecip = .Recipients.Add(SendAddr)
>
>After doing some testing, I found that the code will work provided that
>you
>first OPEN MS Outlook. In previous versions, you didn't have to have
>outlook
>open, and it would still add the e-mail to the outbox.
>
>If there's a fix to where you wouldn't need to open Outlook, I'd love
>to
>know.
>
>FYI, the error code if you don't first open Outlook is Err = 287. It
>would
>error out upon hitting the .recipients.add statement. With Outlook
>opened
>first, all runs well.
I know this is a long shot, but your problem may have been caused by
timing issues. Perhaps the new version of Outlook is taking longer to
open. The code, trying to be helpful and efficient, continues on
without waiting for CreateObject to finish and discovers that Outlook
is not open yet. That would explain why it works when Outlook is
already open. BTW, CreateObject seems never to create more than one
instance of Outlook. Try some DoEvent's in a loop (maybe 2000 times)
after your CreateObject call to see if that's the case. It's true
that the 'Set objOutlookMsg = objOutlook.CreateItem(olMailItem)' line
seems like it might require Outlook to be open, but perhaps it
doesn't. You can also combine this with Tom's suggestion by putting
objOutlook.Visible = True right before the DoEvents loop.
James A. Fortune
CD********@FortuneJames.com
This thread has been closed and replies have been disabled. Please start a new discussion. Similar topics
by: C-man |
last post by:
Basically I have this little program that will look through directories and
rename any file it finds. The renaming that takes place is like removing of
dashes or Caps the first letter from each...
|
by: owen |
last post by:
Generally speaking, what does it mean when I see a "button" with red text
showing this message instead of the control I've dragged onto the web form
in Design View.? (But the page works fine at...
|
by: Nick |
last post by:
Hi,
I have a windows application, wherein the solution consists of 5 projects.
When I try to create a setup and deployment project for this solution, I'm
somehow unable to add anything in...
|
by: John Baker |
last post by:
Hi:
I would like to know how to create a temp DB to store the data in a table while I do
something else with the table.
Specifically, how do I
create the temp
remove the temp
I want to be...
|
by: Pawan |
last post by:
Hi Guys,
I have this current assignment where I have to develop online forms for
local municipal authorities. I have to use adobe acrobat to create online
forms from PDFs (which I have never done...
|
by: LIN |
last post by:
Hello,
Greetings. I am creating a web site which will contain lot of articles. I
had been planning to create simple HTML page on the server everytime i
posted a article (eg. article12.html )....
|
by: chris |
last post by:
I know I've asked this before, but I didn't really get an answer and I
bet it's because I didn't explain myself very well. Here goes again.
I have this code:
Dim arrData(intNoOfRows,...
|
by: Mats Lycken |
last post by:
Hi,
I'm creating a CMS that I would like to be plug-in based with different
plugins handling different kinds of content.
What I really want is to be able to load/unload plugins on the fly
without...
|
by: epigram |
last post by:
I'm dynamically creating a number of radio buttons on my aspx page based
upon data read from a db. Each radio button has autopostback turned on.
I'm experiencing two problems.
1) I am reading...
|
by: Gladiator |
last post by:
Hai all,
I have Db2 installed in a partition environment . There are 4 partitons
on which i created the instance. can any one tell me if i can create a
database on the required partitons .........
|
by: ryjfgjl |
last post by:
In our work, we often receive Excel tables with data in the same format. If we want to analyze these data, it can be difficult to analyze them because the data is spread across multiple Excel files...
|
by: BarryA |
last post by:
What are the essential steps and strategies outlined in the Data Structures and Algorithms (DSA) roadmap for aspiring data scientists? How can individuals effectively utilize this roadmap to progress...
|
by: nemocccc |
last post by:
hello, everyone, I want to develop a software for my android phone for daily needs, any suggestions?
|
by: Sonnysonu |
last post by:
This is the data of csv file
1 2 3
1 2 3
1 2 3
1 2 3
2 3
2 3
3
the lengths should be different i have to store the data by column-wise with in the specific length.
suppose the i have to...
|
by: Oralloy |
last post by:
Hello folks,
I am unable to find appropriate documentation on the type promotion of bit-fields when using the generalised comparison operator "<=>".
The problem is that using the GNU compilers,...
|
by: jinu1996 |
last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven...
|
by: Hystou |
last post by:
Overview:
Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows...
|
by: tracyyun |
last post by:
Dear forum friends,
With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each...
|
by: agi2029 |
last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing,...
| |
