[Trentham]

I'm having a sport of bother using email via Outlook in VB within Access.

The procedure below is called to send a number of emails and all works OK. If I run the process again, it simply hangs (although it looks as though it managed to send the first message). Presumably Outlook is waiting/looking for something. Have I perhaps not closed the first process correctly? The basis of the code was grabbed from the Micro$oft site (which may be the root of the problem!)


Sub SendEmail(stTo As String, stPath As String)
' Start Outlook. If it's already running, we'll use the same instance...

Dim olApp As Outlook.Application
Set olApp = CreateObject("Outlook.Application")

' Logon. Doesn't hurt if we are already running and logged on...

Dim olNs As Outlook.NameSpace
Set olNs = olApp.GetNamespace("MAPI")
olNs.Logon

' Send a message

Dim olMail As Outlook.MailItem
Set olMail = olApp.CreateItem(olMailItem)

' Fill out & send message...

With olMail
.To = stTo
.Subject = "Test attached file"
.Body = "File attached" & vbCrLf & stTo & vbCrLf & stPath
.Attachments.Add stPath
.Send
End With

' Clean up...

olNs.Logoff

Set olNs = Nothing
Set olMail = Nothing
Set olApp = Nothing

End Sub

[MustBNuts]

I don't have Outlook installed (don't really want to), but notice in your code that you reference olMailItem when you set olMail, but where is your dim for olMailItem....

have you stepped through the code on both the first and second instances?

MBN

[Trentham]

That's a very good question! I lifted the code from http://support.microsoft.com/?kbid=220595 and there's no reference to it! I'll stick one in and see what happens.

I also would rather not have Outlook running but it seems I need it for this.

Stepping through doesn't help since it goes into one of the statements and never comes back again!

The whole process has no problems if Outlook is actually running in the first place.

[Rockn]

I was just reading something on this last night and cannot find the chapter at the moment. It had to do with closing the current session prior to open ing a new one, something to that effect.

[MustBNuts]

Stepping through doesn't help since it goes into one of the statements and never comes back again!

Doesn't it ever come back on the first pass, in order to complete the cleanup? At which stmt does it disappear?

MBN

PS: just took a look at that code from MS....if I were you, I'd start a new project, copy the whole thing in, and make sure it works as written. When that works, piece by piece remove the references to the other items (contact and appointment), and at each step test for sending success. But if you haven't tested the MS code in its entirety, you don't know if it will work to begin with.

[Trentham]

On the first pass it works fine. All statements are executed and the thing is closed proerly (assuming the code is correct!). The second time through it goes into

Set olMail = olApp.CreateItem(olMailItem)

never to appear again and the task has to be aborted. Even then, there is still an outlook.exe process running which also has to be aborted before the thing can be tried again.

I'll see whether the MS code is as rugged as I'd like.

I can get my process to work fine if I stick in a 'start up outlook' with
RetVal = Shell("outlook", vbMinimizedNoFocus)
although it doesn't start minimised and it does get the focus. Also a new instance starts every time and I've not (yet) found a way to close it down after I've sent the emails!


In response to an earlier question...
"but where is your dim for olMailItem"
olMailItem is, of course, an intrinsic constant.

[MustBNuts]

Okay, I went ahead and installed Outlook (I have 2003), then used the MS version of the code - it worked.

I then used yours, and yes, it worked on two consecutive runs....the only difference is that I used a click event to point to your sub, and while in the click event I set the stTo and sPath variables there.

I can only assume, then, that it may have something to do with your attachment or address.....

I also do not have a problem with outlook opening. I just get this small warning window (jpg attached) when I click Yes, it sends the email.

MBN

[MustBNuts]

PS: just to add to your confusion.....it behaved differently with and without the msgbox after the .send.

hmmmmmmm

MBN

[MustBNuts]

Okay, had to disable my Norton AV and still found that if the process was too fast (I tried to send 3 in rapid succession), at least one of them did not arrive and the little app threw an error msg.

How many emails are you trying to put out at any given time?

MBN

[Trentham]

In my testing I'm sending 3 messages. My AV product is AVG free version which doesn't interecpt the outgoing messages in the same way and so is not a speed problem.

Also, I'm using Outlook 2000. I'm expecting to get the latest version later this week and I'll see if it behaves the same.

WRT the initiating of this procedure, I've now incorporated the code into the original click event and it behaves the same way.

Thanks for all your efforts. It's most helpful and suggests that my environment or version 2000 of Outlook may be behind the problem!

[MustBNuts]

Glad to help, it was interesting to do.......

MBN

[Trentham]

Now don't you just hate it when...
You copy the whole thing to a different logical disk drive and the problem goes away! (and no, it wasn't a disk space issue).

To err is human but to truly **** things up akes a computer!

[MustBNuts]

from where to where?

Also, do you get the Yes/No msgbox when it accesses Outlook? Have you found any way to get rid of it?

MBN

[Trentham]

Went from drive L to drive C. Same physical drive. On checking I see that L is FAT (!) while C is FAT32.

I've never had the msg yes/no box appear. I'm not sending a jpg, just a txt, though I don't see that that would make any difference.

In an earlier incarnation I was sending via Outlook Express (though that couldn't handle attachments) and had to send an option to allow external programs to send emal silently.

[MustBNuts]

hmmmm, you aren't getting the yes/no box (I attached a jpg of it ealier)?

Are you still using the option to send silently? What sort of code?

MBN