Very incorrect. It was added to a post-SP1 update of Outlook 2000, built
into Outlook 2002 and 2003. SP's for each build made changes to the
security, so it's possible a later update changed so that a property that
was previously ok now triggers it. But again... a good dev updates their
apps to avoid the alert.

--
Diane Poremsky [MVP - Outlook]
Author, Teach Yourself Outlook 2003 in 24 Hours
Need Help with Common Tasks? http://www.outlook-tips.net/beginner/
Outlook 2007: http://www.slipstick.com/outlook/ol2007/

Outlook Tips by email:


Outlook Tips: http://www.outlook-tips.net/
Outlook & Exchange Solutions Center: http://www.slipstick.com
Subscribe to Exchange Messaging Outlook newsletter:



"Stroller" wrote in message
. co.uk...
On Tue, 19 Jun 2007 15:12:57 +0100, Diane Poremsky wrote
(in article ):

without knowing your version of outlook, those are the best options. Does
the vendor have a version that bypasses the security guard? (They've had
7
yrs to work on it.)

Sorry... I meant to say in my original post that we're exclusively using
Outlook 2003 in this office.

I believe that this message has only started appearing on one machine
recently, and that it has more up-to-date patches than other PCs on the
network. I'll email the client today to check the status with the other
PCs.

I note the "7 years" comment that you & another poster made. The senior
support guy for the CRM vendor asserts:

This message is an annoying and new security feature of Outlook
2002 and 2003.

Is this incorrect?

Stroller.