Since we can't look over your shoulder, you'll have to give us some clues about the problems you're encountering.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx

"LongWayFromHome" wrote in message ...
I'm afraid I need some help doing that. The first bugs I hit are variable
types that don't work in Outlook VBA, and I can't readily see what the
equivalents are.

Thanks.
--
Dave


"Sue Mosher [MVP-Outlook]" wrote:

Some anti-virus programs block access to Outlook through CreateObject() and GetObject(). A possible solution is the one I originally suggested -- modify the code to run in Outlook VBA. That should also eliminate the security prompts.

"LongWayFromHome" wrote in message ...
Sue, you were correct. I had failed to set up the list as a table. That is
fixed, and the macro definitely runs -- but no emails go out. I purposely
have not installed "Express ClickYes" yet in order to get confirmation on my
test emails, but no warning messages appear. I'm not sure what to check
next, since I don't see any error messages.

I carefully repeated the MVP instructions for the Directory merge document.
I placed the email address in the 1st column and the file name in the 2nd.
Then I ran the merge to create the MailList, which looks like the sample. I
close both of those, open my message merge document, execute it to a new
document, which produces the 9 test messages. With the 9 messages on screen,
I run the macro. When the FileOpen dialog appears, I select my MailList. I
get a lot of nice, reassuring window flashes, but Outlook (which is running)
doesn't respond.

When I step through the macro, I am a little mystified when this code
appears to execute, even though Outlook is running:

'Check if Outlook is running. If it is not, start Outlook
On Error Resume Next
Set oOutlookApp = GetObject(, "Outlook.Application")
If Err 0 Then
Set oOutlookApp = CreateObject("Outlook.Application")
bStarted = True
End If

Is that a clue?

Thanks!
--
Dave


"Sue Mosher [MVP-Outlook]" wrote:

On the surface, it says that there's no Tables(1) in the MailList document. You can use the Locals window to check the Tables collection.