S
Skreemer
in this ( http://support.microsoft.com/default.aspx?
scid=kb;EN-US;262701 ) article it describes some of the
security features of outlook. We are using VisualFoxPro6
to generate E-mails and let us know when certain processes
have finished. Someone ran a security update recently and
now one of the machines halts when FoxPro attempts to send
a file. The particular piece I am having a problem with is
this.
Item.Send
When you run a program that uses the Outlook object model
to call the Send method, you receive a warning message.
This warning message tells you that a program is trying to
send mail on your behalf and asks if you want to allow the
message to be sent. The warning message contains both a
Yes and a No button, however, the Yes button is not
available until five seconds have passed since the warning
message appeared. You can dismiss the warning message
immediately if you click No. When you click No, the Send
method returns an E_FAIL error in the C or C++ programming
languages.
Are there any work arounds or registry entries I can make
or update to disable this warning message?
scid=kb;EN-US;262701 ) article it describes some of the
security features of outlook. We are using VisualFoxPro6
to generate E-mails and let us know when certain processes
have finished. Someone ran a security update recently and
now one of the machines halts when FoxPro attempts to send
a file. The particular piece I am having a problem with is
this.
Item.Send
When you run a program that uses the Outlook object model
to call the Send method, you receive a warning message.
This warning message tells you that a program is trying to
send mail on your behalf and asks if you want to allow the
message to be sent. The warning message contains both a
Yes and a No button, however, the Yes button is not
available until five seconds have passed since the warning
message appeared. You can dismiss the warning message
immediately if you click No. When you click No, the Send
method returns an E_FAIL error in the C or C++ programming
languages.
Are there any work arounds or registry entries I can make
or update to disable this warning message?