Annoying Message (2000 and up)

Topic

New Reply

We have been trying to send e-mail from Access. Whether we use SendObject or Automation, we get an annoying message from Outlook for each e-mail we try to send. This message is:
“A program is trying to automatically send e-mail on your behalf. Do you want to allow this?”

In MSKB, we found some references to this, and it seems that the only way around it is by resetting options in Message Server (which we aren’t using) or by creating a plug-in.

Is there some (hopefully easier) way around this?

Reply | Quote

Replies

Mark

Would you be so kind as to tell us the MSKB article numbers so that we can go get them.

I too would like to solve some automation issues, though from within Outlook and its VBA model.

Thanks

Wassim

Reply | Quote

I think I started with Q290498 and then followed the links.

Reply | Quote

I think I started with Q290498 and then followed the links.

Reply | Quote

Mark

Would you be so kind as to tell us the MSKB article numbers so that we can go get them.

I too would like to solve some automation issues, though from within Outlook and its VBA model.

Thanks

Wassim

Reply | Quote

See post 317048.

Reply | Quote

Thanks, but that basically is what we’ve already come up with. We were just hoping there was something else. Oddly enough, Outlook Express has an option that controls this very thing, yet Outlook doesn’t. I suppose it is so Outlook is more secure, but considering someone discovers a new security flaw in Outlook about every other day, I’m wondering how much removing options really helps!

Reply | Quote

Thanks, but that basically is what we’ve already come up with. We were just hoping there was something else. Oddly enough, Outlook Express has an option that controls this very thing, yet Outlook doesn’t. I suppose it is so Outlook is more secure, but considering someone discovers a new security flaw in Outlook about every other day, I’m wondering how much removing options really helps!

Reply | Quote

See post 317048.

Reply | Quote

I use Access to send a lot of automated messages, and was thoroughly frustrated with the same security feature. What I found to work well is a little program called ‘Express ClickYes’ from Express Soft. This program will automatically answer this security prompt, and without the 5 second delay either. In order to integrate it I have Access start it whenever it is needed by including it in the SendObject macro, placing the RunApp command ahead of the SendObject command. Once the sending is finished I just turn off the ClickYes program (it can be code-controlled to activate and deactivate on command, but I havn’t gotten that far yet).

Reply | Quote

David,

Thanks. I did stumble across ClickYes, but thought it would still have to wait for that 5 second delay. Since we are trying to do automatic submittal of multiple e-mails (one after another), we didn’t know how this would interact with it. From what you said, though, it might work better than we had suspected. Probably worth a try. Thanks again!

Reply | Quote

It is nice, there is no delay whatsoever with the security prompt. ClickYes watches for it and answers it immediately. Whether it is for just one message or a series of messages it is a very good solution to the problem. One possible way of using it is to have it always running but in its ‘idle’ mode, and using the example code to activate or deactivate it as necessary. I’ve suggested to the author that the program include a command line option to close it completely so it can be activated and deactivated using RunApp instead of the more cumbersome code, but that remains to be adopted (if ever). But for system resources I prefer to have as little running as necessary so I rely on having it turned on only when it is needed.

Reply | Quote

It is nice, there is no delay whatsoever with the security prompt. ClickYes watches for it and answers it immediately. Whether it is for just one message or a series of messages it is a very good solution to the problem. One possible way of using it is to have it always running but in its ‘idle’ mode, and using the example code to activate or deactivate it as necessary. I’ve suggested to the author that the program include a command line option to close it completely so it can be activated and deactivated using RunApp instead of the more cumbersome code, but that remains to be adopted (if ever). But for system resources I prefer to have as little running as necessary so I rely on having it turned on only when it is needed.

Reply | Quote

David,

Thanks. I did stumble across ClickYes, but thought it would still have to wait for that 5 second delay. Since we are trying to do automatic submittal of multiple e-mails (one after another), we didn’t know how this would interact with it. From what you said, though, it might work better than we had suspected. Probably worth a try. Thanks again!

Reply | Quote

David,

I have not had any luck with the 5 second delay. Your post mentions that the program can automatically answer the security prompt without the 5 second delay.

Any assistance would be appreciated.

Thanks,
John

Reply | Quote

Unfortunately I don’t think I can offer much in the way of assistance. When I have Access launch the program it’s by using a simple command line for the program, no switches or settings of any sort. The only options I know of are to have it start on logon and start suspended, neither of which are selected, and I havn’t found any ‘hidden’ settings in either the registry or in any .ini file. This leads me to think that the difference that is causing the delay to not be over-ruled by the program might be found in your Windows settings somehow. For what it’s worth, I’m running Win2K Pro (SR4) and Office2K Pro (SP3).

Reply | Quote

David,

What command line text are you using to call/close ClickYes?

Thanks,
John

Reply | Quote

David,

What command line text are you using to call/close ClickYes?

Thanks,
John

Reply | Quote

The command I use is RunApp with the Command Line argument “C:Program FilesExpressClickYesClickYes.exe”. This starts the program in its ‘active’ mode (ie, not suspended), and then as fast as the SendObject command causes Outlook to pop up its warning message ClickYes answers it – no delay whatsoever. I’ve been very happy with the way it works, whether it is with a single email or a whole string of them. I would like to see the program be able to be shut down via command line to complete the process cleanly, but for now I do this last part manually.

Reply | Quote

David,

I too tried RunApp with the Command Line argument. Unfortunately I get multiple calls to the command line. I see two or more icons in the systray and can’t seem to close them. It must be my coding.

John

Reply | Quote

Unfortunately I don’t think there is any to close them automatically; I close them manually once my mailings have finished running. The sample VBA code that the author provides allows the program to be toggled between active & suspended, but no code to turn it off. If there is a piece of VBA code that can target and kill a specific application, I don’t know of it.

Reply | Quote

Unfortunately I don’t think there is any to close them automatically; I close them manually once my mailings have finished running. The sample VBA code that the author provides allows the program to be toggled between active & suspended, but no code to turn it off. If there is a piece of VBA code that can target and kill a specific application, I don’t know of it.

Reply | Quote

If you’re looking at trying to close a program that is running in the System Tray, you could have a look at the thread starting with post 327471 over on the Excel Board – especially post 332411. This is not using Excel VBA – and you may wish to take a deep breath before working through some of the code.

Reply | Quote

If you’re looking at trying to close a program that is running in the System Tray, you could have a look at the thread starting with post 327471 over on the Excel Board – especially post 332411. This is not using Excel VBA – and you may wish to take a deep breath before working through some of the code.

Reply | Quote

David,

I too tried RunApp with the Command Line argument. Unfortunately I get multiple calls to the command line. I see two or more icons in the systray and can’t seem to close them. It must be my coding.

John

Reply | Quote

The command I use is RunApp with the Command Line argument “C:Program FilesExpressClickYesClickYes.exe”. This starts the program in its ‘active’ mode (ie, not suspended), and then as fast as the SendObject command causes Outlook to pop up its warning message ClickYes answers it – no delay whatsoever. I’ve been very happy with the way it works, whether it is with a single email or a whole string of them. I would like to see the program be able to be shut down via command line to complete the process cleanly, but for now I do this last part manually.

Reply | Quote

Unfortunately I don’t think I can offer much in the way of assistance. When I have Access launch the program it’s by using a simple command line for the program, no switches or settings of any sort. The only options I know of are to have it start on logon and start suspended, neither of which are selected, and I havn’t found any ‘hidden’ settings in either the registry or in any .ini file. This leads me to think that the difference that is causing the delay to not be over-ruled by the program might be found in your Windows settings somehow. For what it’s worth, I’m running Win2K Pro (SR4) and Office2K Pro (SP3).

Reply | Quote

David,

I have not had any luck with the 5 second delay. Your post mentions that the program can automatically answer the security prompt without the 5 second delay.

Any assistance would be appreciated.

Thanks,
John

Reply | Quote