J
Joe Pride
My organization recently upgraded all our machines to Vista Enterprise and
Office Professional 2007. I had a Visual Basic script in a Microsoft Access
database, basically a phone and email tree, that I used to be able to use to
automatically generate emails in order to brief a large number of our
staffers from a tailor-made query on short notice.
The security update in Outlook 2007 is blocking it entirely. When I create
an Outlook Mail Item and then use the item.Recipients.Add(Address as String)
method to add all my recipients to the Mail Item, I get a 287 error.
I understand the need to control Outlook automation in VBA, but couldn't
that still be done using the "Another application is trying to access your
email" alert box that used to come up and the five-second send delay? I
submit that there must be a middle ground where the user can exercise control
over the emails being sent, instead of getting a fatal error and crashing.
There are workarounds, but they require installing DLL's on every computer or
inserting VBA script into every user's Outlook macros. Could this perhaps be
addressed in a future Windows Update patch?
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...27bc1&dg=microsoft.public.outlook.program_vba
Office Professional 2007. I had a Visual Basic script in a Microsoft Access
database, basically a phone and email tree, that I used to be able to use to
automatically generate emails in order to brief a large number of our
staffers from a tailor-made query on short notice.
The security update in Outlook 2007 is blocking it entirely. When I create
an Outlook Mail Item and then use the item.Recipients.Add(Address as String)
method to add all my recipients to the Mail Item, I get a 287 error.
I understand the need to control Outlook automation in VBA, but couldn't
that still be done using the "Another application is trying to access your
email" alert box that used to come up and the five-second send delay? I
submit that there must be a middle ground where the user can exercise control
over the emails being sent, instead of getting a fatal error and crashing.
There are workarounds, but they require installing DLL's on every computer or
inserting VBA script into every user's Outlook macros. Could this perhaps be
addressed in a future Windows Update patch?
----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.
http://www.microsoft.com/office/com...27bc1&dg=microsoft.public.outlook.program_vba