Its a custom meeting form IPM.Appointment. The reason I was calling it an
error message was because the user of Outlook 2003 gets this security warning
sometimes.

Thanks

"Sue Mosher [MVP]" wrote:

Meeting? Is this a custom Appointment form? What is the value of the
MessageClass property on the received item that has this behavior?

I wouldn't call this an error message, BTW. It's a security warning.
--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"BuddyWork" wrote in message
...
Hello Sue,

The form does called the CreateObject to create a C# ActiveX object. This
is
the only ActiveX object that is used.

In Outlook 2007 users have not reported this macro error message.

In Outlook 2003 users are saying they are not seeing the macro error
message
all the time. It sometime appears when the meeting arrives in their inbox
they get the error message sometimes. They have the preview feature
enabled.
But they are saying they do not get this error all the time which means
its
hard for me to reproduce. The strange thing is that the message was on
their
screen and when I asked them to create the same meeting then the error did
not appear.

Their normal.dot does not include any macros.

Thanks,


"Sue Mosher [MVP]" wrote:

Does the form use any ActiveX controls that are not present in Outlook
2003?
Have you tried publishing the form with Outlook 2003 instead of Outlook
2007? Is the Outlook 2003 using Word as the email editor? Are there
macros
in the Normal.dot file?

"BuddyWork" wrote in message
...

Found it and the Send form definition with item is already unchecked.
"Sue Mosher [MVP]" wrote:

Sounds like you might have a very old version of Outlook 2003,
without
service packs, that gives a confusing message. Make sure the
form
is
published with the "send form definition with item" box on the
(Properties)
page in design mode unchecked.

"BuddyWork" wrote:

I've created a custom outlook form using VB Script and in
Outlook
2003
the
users gets the message 'Macros have been disabled. Macros
might
contain
viruses or other security hazards. Do not enable this content
unless
you
trust the source of this file'. In Outlook 2007 the users do
not
get
this
message. The VB Script does not call into any macros so I
cannot
understand
why this is happening.