Yes, it means the administrator in your office has set the CheckAdminSettings value to look to a public folder for settings that control the behavior of the "object model guard." Under that scenario, your VBA intrinsic Application object is not "trusted," and thus you will get security prompts.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx


"Keith ''StarPilot'' Barrows" wrote in message ...
Security Mode: Administrator Controlled

That's a bad thing (for me), huh? :|

--
Keith ''StarPilot'' Barrows
ASPInsider
http://sol3.net/blogs/starpilot


"Sue Mosher [MVP-Outlook]" wrote:

In Outlook | Help About on the work system, what does it show as the setting for "Security Mode"?



"Keith 'StarPilot' Barrows" wrote in message ...
Hmm. I've been watching this problem and comparing notes between my work
system (where it's broken) and my home system (where it works).

At work, I get the annoyance message and have to "allow" access for 1, 5 or
10 minutes.

At home, I launch Outlook, am asked if I want to allow macros, click yes and
am never bothered again.

Both systems are Win XP Pro, SP2. Both systems are on domains (yes, I run a
DC at home). The home DC has a minimum set of Policies. The work system can
take 3 minutes just loading policies. Both systems are running Outlook 2003.
Work is on SP1, home is whatever the latest is via windows update.

So, why does it work in one place and not the other??

"Sue Mosher [MVP-Outlook]" wrote:

This is an Outlook VBA procedure, a COM add-in, or an external VB application?


"Keith 'StarPilot' Barrows" wrote in message ...
I am just not getting this to work.

Outlook 2003, SP1
Windows XP, SP2

Here is a snippet of code that is failing:

Private Sub sortIncoming(ByRef mail As MailItem)
On Error GoTo errHandler
Dim targetPst As String
Dim targetFolders
Dim sourceDomain As String
Dim sourceList As String
Dim sourceAddress As String
Dim myExplorers As Outlook.Explorers
Dim pstFolder As MAPIFolder
Dim targetFolder As MAPIFolder
Dim i As Integer
Dim j As Integer
' This is *supposed* to bypass the object guard...
Dim strID As String
Dim olNS As Outlook.NameSpace
Dim olMail As Outlook.MailItem

strID = mail.EntryID
Set olNS = Application.GetNamespace("MAPI")
Set olMail = olNS.GetItemFromID(strID)

' This is still tripping the object guard!!
sourceAddress = olMail.Recipients.Item(1).Address
....
....
....

exitHandler:
Set olMail = Nothing
Set olNS = Nothing
Exit Sub

errHandler:
Resume Next

End Sub

Any ideas *WHY* it's still tripping the object guard???

--
Keith 'StarPilot' Barrows
ASPInsider
http://sol3.net/blogs/starpilot


"Sue Mosher [MVP-Outlook]" wrote:

See http://www.outlookcode.com/d/sec.htm for your options with regard to the "object model guard" security in Outlook 2000 SP2 and later versions.


"ms news" wrote in message ...
They are any possibility to disable the security alerts on outlook XP/2003?,
I thing trought the registry.

I have a Visual Basic application that access to my outlook messages. But
the security alert is not allowing me to access all the time to the savefile
method