Chuck,

Make sure that WshShell.AppActivate parameter matches the Oulook Dialog title. You can also play with the time script waits for a dialog. To see script execution window you can temporay use

RUN /N4 cscript waitforoutlook.vbs

You can also use Wscript.Echo "..." to display messages.

'VBScript WaitForOutlook.VBS
Set WshShell = Wscript.CreateObject("WScript.Shell")
' this waits 20 seconds from launch to action.  You can experiment with
' shorter or longer durations as necessary
Wscript.Echo "Waiting for Dialog"
Wscript.Sleep 20000 
WshShell.AppActivate "Microsoft Outlook"
' wait 1/10th second after requesting activation of the Outlook Window
Wscript.Sleep 100 
WshShell.SendKeys "Y"

>Sergey
>Thanks for the links. I am at a disadvantage with not be able to load stuff on our servers or individuals PC's. State government! What was interesting was the one FAQ the Ed Rauh wrote, except I can't seem to get it to work. The timeout doesn't even happen. All I did was add the script,
>

RUN /N7 cscript waitforoutlook.vbs

>after the createitem and before send. I get no errors but I don't know how to see if the script ran. I guess I will have to have the users deal with the messages.
>
>>There're a few ways to get around Outlook warnings but you should understand implications of each of them:
>>- Free Express ClickYes program at http://www.express-soft.com/mailmate/clickyes.html.
>>- Redemption at http://www.dimastr.com/redemption/home.htm.
>>- How do I avoid the annoying Outlook dialog sending Outlook automation or MAPI email? FAQ #8155
>>- OL2000: Administrator Information About the Outlook E-mail Security Update mskb #Q263297.