Macros have been disabled error Message with Custom forms

  • Thread starter BuddyWork
  • Start date Views 4,066
Status
Not open for further replies.
B

BuddyWork

Hello,

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.
 
S

Sue Mosher [MVP]

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.

Sue Mosher

"BuddyWork" wrote:


> Hello,

> 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.
 
B

BuddyWork

Hello Sue,

Thank you for your response. Please can you point me to where the location

where the 'Send form definition with item' setting exist.

"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.
> > Sue Mosher
> > >

> "BuddyWork" wrote:
>
> > Hello,
> > 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.
 
S

Sue Mosher [MVP]

It's right wherere I said it was -- on the (Properties) page in the form's

design mode.

Sue Mosher

"BuddyWork" <BuddyWork> wrote in message

news:1C18ADF1-0135-4601-AFCA-1371CAB28EB4@microsoft.com...
> Hello Sue,

> Thank you for your response. Please can you point me to where the location
> where the 'Send form definition with item' setting exist.

> "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:
> >
> > > Hello,
> >> > 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.
 
B

BuddyWork

I am developing in Outlook 2007, but my users are Outlook 2003 and 2007.

"BuddyWork" wrote:


> Hello Sue,

> Thank you for your response. Please can you point me to where the location
> where the 'Send form definition with item' setting exist.

> "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.
> > > > Sue Mosher
> > > > > > > > "BuddyWork" wrote:
> >
> > > Hello,
> > > > 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.
 
B

BuddyWork

Hello Sue,

I don't see it.

I am developing in Outlook 2007, but my users are Outlook 2003 and 2007.

Thanks,

"Sue Mosher [MVP]" wrote:


> It's right wherere I said it was -- on the (Properties) page in the form's
> design mode.
> > Sue Mosher
> > >

> "BuddyWork" <BuddyWork> wrote in message
> news:1C18ADF1-0135-4601-AFCA-1371CAB28EB4@microsoft.com...
> > Hello Sue,
> > Thank you for your response. Please can you point me to where the location
> > where the 'Send form definition with item' setting exist.
> > "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:
> >
> >> > Hello,
> >> >> > 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.


>
 
S

Sue Mosher [MVP]

Look again.

Step 1: Open the form in design mode.

Step 2: Switch to the (Properties) page, which is the next to last page on

the right.

Step 3: Look for the "Send form definition with item" check box on the right

side of the page, under the Change Small Icon button.

Sue Mosher

"BuddyWork" <BuddyWork> wrote in message

news:F1DC50C9-6294-48EE-9899-02F919A34B45@microsoft.com...
> Hello Sue,

> I don't see it.

> I am developing in Outlook 2007, but my users are Outlook 2003 and 2007.

> Thanks,

> "Sue Mosher [MVP]" wrote:
>
> > It's right wherere I said it was -- on the (Properties) page in the
> > form's
> > design mode.
>

>> "BuddyWork" <BuddyWork> wrote in message
> > news:1C18ADF1-0135-4601-AFCA-1371CAB28EB4@microsoft.com...
> > > Hello Sue,
> >> > Thank you for your response. Please can you point me to where the
> > > location
> > > where the 'Send form definition with item' setting exist.
> >> > "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:
> > >
>> >> > Hello,
> > >>> >> > 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.
 
B

BuddyWork

Hello Sue,

Found it and the Send form definition with item is already unchecked.

Thanks

"Sue Mosher [MVP]" wrote:


> Look again.

> Step 1: Open the form in design mode.

> Step 2: Switch to the (Properties) page, which is the next to last page on
> the right.

> Step 3: Look for the "Send form definition with item" check box on the right
> side of the page, under the Change Small Icon button.
> > Sue Mosher
> > >

> "BuddyWork" <BuddyWork> wrote in message
> news:F1DC50C9-6294-48EE-9899-02F919A34B45@microsoft.com...
> > Hello Sue,
> > I don't see it.
> > I am developing in Outlook 2007, but my users are Outlook 2003 and 2007.
> > Thanks,
> > "Sue Mosher [MVP]" wrote:
> >
> >> It's right wherere I said it was -- on the (Properties) page in the
> >> form's
> >> design mode.
> >
> >> "BuddyWork" <BuddyWork> wrote in message
> >> news:1C18ADF1-0135-4601-AFCA-1371CAB28EB4@microsoft.com...
> >> > Hello Sue,
> >> >> > Thank you for your response. Please can you point me to where the
> >> > location
> >> > where the 'Send form definition with item' setting exist.
> >> >> > "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:
> >> >
> >> >> > Hello,
> >> >> >> >> > 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.


>
 
S

Sue Mosher [MVP]

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?

Sue Mosher

"BuddyWork" <BuddyWork> wrote in message

news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...

> 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.

>

>
>>
 
B

BuddyWork

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?
> > Sue Mosher
> > >

> "BuddyWork" <BuddyWork> wrote in message
> news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...
> > 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.
> >
> >
> >>


>
 
S

Sue Mosher [MVP]

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

"BuddyWork" <BuddyWork> wrote in message

news:CD9FF8BA-1F77-4943-9D58-ABC24CAABCBF@microsoft.com...
> 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" <BuddyWork> wrote in message
> > news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...
> >> > 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.
> > >
>> >
>> >>

>

>
>>
 
B

BuddyWork

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
> > >

> "BuddyWork" <BuddyWork> wrote in message
> news:CD9FF8BA-1F77-4943-9D58-ABC24CAABCBF@microsoft.com...
> > 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" <BuddyWork> wrote in message
> >> news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...
> >> >> > 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.
> >> >
> >> >
> >> >
> >
> >
> >>


>
 
S

Sue Mosher [MVP]

I'm not sure you answered my actual question, which was: What is the actual

value of the MessageClass property on the received item that has this

behavior? Is the user getting the message only when they preview the item,

only when they open the item, or both? Also, do you get the same behavior if

you publish the form with Outlook 2003 instead of 2007?

When I was asking about ActiveX, I was asking about controls on the form's

design surface, not the code behind the form. You're not using any of the

new controls that come with Outlook 2007, are you?

Sue Mosher

"BuddyWork" <BuddyWork> wrote in message

news:35B1C691-9110-4BE9-95D0-69246C788205@microsoft.com...
> Its a custom meeting form IPM.Appointment.

> "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?
>

>> "BuddyWork" <BuddyWork> wrote in message
> > news:CD9FF8BA-1F77-4943-9D58-ABC24CAABCBF@microsoft.com...
> > > 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" <BuddyWork> wrote in message
> > >> news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...
> > >>> >> > 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.
 
B

BuddyWork

Hello Sue,

I believe the MessageClass value is set to IPM.Appointment because I have

not changed it. I could add some debugging information to see what the actual

value is when the security message is displayed.

Correct the user only gets the error when they preview the item sometimes.

There are no Outlook 2007 controls used.

Thanks,

"Sue Mosher [MVP]" wrote:


> I'm not sure you answered my actual question, which was: What is the actual
> value of the MessageClass property on the received item that has this
> behavior? Is the user getting the message only when they preview the item,
> only when they open the item, or both? Also, do you get the same behavior if
> you publish the form with Outlook 2003 instead of 2007?

> When I was asking about ActiveX, I was asking about controls on the form's
> design surface, not the code behind the form. You're not using any of the
> new controls that come with Outlook 2007, are you?
> > Sue Mosher
> > >

> "BuddyWork" <BuddyWork> wrote in message
> news:35B1C691-9110-4BE9-95D0-69246C788205@microsoft.com...
> > Its a custom meeting form IPM.Appointment.
> > "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?
> >
> >> "BuddyWork" <BuddyWork> wrote in message
> >> news:CD9FF8BA-1F77-4943-9D58-ABC24CAABCBF@microsoft.com...
> >> > 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" <BuddyWork> wrote in message
> >> >> news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...
> >> >> >> >> > 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.


>
 
S

Sue Mosher [MVP]

If you are using a published form, the message class cannot be

IPM.Appointment, because that's the standard form's class. If you are not

using a published form, then it's not going to be fully functional.

Sue Mosher

"BuddyWork" <BuddyWork> wrote in message

news:B3ABF2EA-3033-446C-A55A-A6E49DE8EA61@microsoft.com...
> Hello Sue,

> I believe the MessageClass value is set to IPM.Appointment because I have
> not changed it. I could add some debugging information to see what the
> actual
> value is when the security message is displayed.

> Correct the user only gets the error when they preview the item sometimes.

> There are no Outlook 2007 controls used.

> Thanks,

> "Sue Mosher [MVP]" wrote:
>
> > I'm not sure you answered my actual question, which was: What is the
> > actual
> > value of the MessageClass property on the received item that has this
> > behavior? Is the user getting the message only when they preview the
> > item,
> > only when they open the item, or both? Also, do you get the same behavior
> > if
> > you publish the form with Outlook 2003 instead of 2007?
>

>> When I was asking about ActiveX, I was asking about controls on the
> > form's
> > design surface, not the code behind the form. You're not using any of the
> > new controls that come with Outlook 2007, are you?
>

>> "BuddyWork" <BuddyWork> wrote in message
> > news:35B1C691-9110-4BE9-95D0-69246C788205@microsoft.com...
> > > Its a custom meeting form IPM.Appointment.
> >> > "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?
> > >
>> >> "BuddyWork" <BuddyWork> wrote in message
> > >> news:CD9FF8BA-1F77-4943-9D58-ABC24CAABCBF@microsoft.com...
> > >> > 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" <BuddyWork> wrote in message
> > >> >> news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...
> > >> >>> >> >> > 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.

>

>
>>
 
B

BuddyWork

When I was debugging the code it was IPM.Appointment but after its published

its IPM.Appointment.Marketer Meeting

Thanks,

"Sue Mosher [MVP]" wrote:


> If you are using a published form, the message class cannot be
> IPM.Appointment, because that's the standard form's class. If you are not
> using a published form, then it's not going to be fully functional.

> > Sue Mosher
> > >

> "BuddyWork" <BuddyWork> wrote in message
> news:B3ABF2EA-3033-446C-A55A-A6E49DE8EA61@microsoft.com...
> > Hello Sue,
> > I believe the MessageClass value is set to IPM.Appointment because I have
> > not changed it. I could add some debugging information to see what the
> > actual
> > value is when the security message is displayed.
> > Correct the user only gets the error when they preview the item sometimes.
> > There are no Outlook 2007 controls used.
> > Thanks,
> > "Sue Mosher [MVP]" wrote:
> >
> >> I'm not sure you answered my actual question, which was: What is the
> >> actual
> >> value of the MessageClass property on the received item that has this
> >> behavior? Is the user getting the message only when they preview the
> >> item,
> >> only when they open the item, or both? Also, do you get the same behavior
> >> if
> >> you publish the form with Outlook 2003 instead of 2007?
> >
> >> When I was asking about ActiveX, I was asking about controls on the
> >> form's
> >> design surface, not the code behind the form. You're not using any of the
> >> new controls that come with Outlook 2007, are you?
> >
> >> "BuddyWork" <BuddyWork> wrote in message
> >> news:35B1C691-9110-4BE9-95D0-69246C788205@microsoft.com...
> >> > Its a custom meeting form IPM.Appointment.
> >> >> > "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?
> >> >
> >> >> "BuddyWork" <BuddyWork> wrote in message
> >> >> news:CD9FF8BA-1F77-4943-9D58-ABC24CAABCBF@microsoft.com...
> >> >> > 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" <BuddyWork> wrote in message
> >> >> >> news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...
> >> >> >> >> >> >> > 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.
> >
> >
> >>


>
 
S

Sue Mosher [MVP]

Debugging how, where? What I'm interested in is the value of the

MessageClass property on the actual received item.

Sue Mosher

"BuddyWork" <BuddyWork> wrote in message

news:2CFD7E5D-F53B-4E19-8F45-ED2CA5A2291C@microsoft.com...
> When I was debugging the code it was IPM.Appointment but after its
> published
> its IPM.Appointment.Marketer Meeting

> Thanks,

> "Sue Mosher [MVP]" wrote:
>
> > If you are using a published form, the message class cannot be
> > IPM.Appointment, because that's the standard form's class. If you are not
> > using a published form, then it's not going to be fully functional.



>

>> "BuddyWork" <BuddyWork> wrote in message
> > news:B3ABF2EA-3033-446C-A55A-A6E49DE8EA61@microsoft.com...
> > > Hello Sue,
> >> > I believe the MessageClass value is set to IPM.Appointment because I
> > > have
> > > not changed it. I could add some debugging information to see what the
> > > actual
> > > value is when the security message is displayed.
> >> > Correct the user only gets the error when they preview the item
> > > sometimes.
> >> > There are no Outlook 2007 controls used.
> >> > Thanks,
> >> > "Sue Mosher [MVP]" wrote:
> >> >> I'm not sure you answered my actual question, which was: What is the
> > >> actual
> > >> value of the MessageClass property on the received item that has this
> > >> behavior? Is the user getting the message only when they preview the
> > >> item,
> > >> only when they open the item, or both? Also, do you get the same
> > >> behavior
> > >> if
> > >> you publish the form with Outlook 2003 instead of 2007?
> > >
>> >> When I was asking about ActiveX, I was asking about controls on the
> > >> form's
> > >> design surface, not the code behind the form. You're not using any of
> > >> the
> > >> new controls that come with Outlook 2007, are you?
> > >
>> >> "BuddyWork" <BuddyWork> wrote in message
> > >> news:35B1C691-9110-4BE9-95D0-69246C788205@microsoft.com...
> > >> > Its a custom meeting form IPM.Appointment.
> > >>> >> > "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?
> > >> >
>> >> >> "BuddyWork" <BuddyWork> wrote in message
> > >> >> news:CD9FF8BA-1F77-4943-9D58-ABC24CAABCBF@microsoft.com...
> > >> >> > 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" <BuddyWork> wrote in
> > >> >> >> message
> > >> >> >> news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...
> > >> >> >>> >> >> >> > 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.
> > >
>> >
>> >>

>

>
>>
 
B

BuddyWork

Hello Sue,

Item.MessageClass is equal to IPM.Appointment Marketer Meeting

Item.Class is equal to 37

Thanks

"Sue Mosher [MVP]" wrote:


> Debugging how, where? What I'm interested in is the value of the
> MessageClass property on the actual received item.

> > Sue Mosher
> > >

> "BuddyWork" <BuddyWork> wrote in message
> news:2CFD7E5D-F53B-4E19-8F45-ED2CA5A2291C@microsoft.com...
> > When I was debugging the code it was IPM.Appointment but after its
> > published
> > its IPM.Appointment.Marketer Meeting
> > Thanks,
> > "Sue Mosher [MVP]" wrote:
> >
> >> If you are using a published form, the message class cannot be
> >> IPM.Appointment, because that's the standard form's class. If you are not
> >> using a published form, then it's not going to be fully functional.

>
> >
> >> "BuddyWork" <BuddyWork> wrote in message
> >> news:B3ABF2EA-3033-446C-A55A-A6E49DE8EA61@microsoft.com...
> >> > Hello Sue,
> >> >> > I believe the MessageClass value is set to IPM.Appointment because I
> >> > have
> >> > not changed it. I could add some debugging information to see what the
> >> > actual
> >> > value is when the security message is displayed.
> >> >> > Correct the user only gets the error when they preview the item
> >> > sometimes.
> >> >> > There are no Outlook 2007 controls used.
> >> >> > Thanks,
> >> >> > "Sue Mosher [MVP]" wrote:
> >> >> >> I'm not sure you answered my actual question, which was: What is the
> >> >> actual
> >> >> value of the MessageClass property on the received item that has this
> >> >> behavior? Is the user getting the message only when they preview the
> >> >> item,
> >> >> only when they open the item, or both? Also, do you get the same
> >> >> behavior
> >> >> if
> >> >> you publish the form with Outlook 2003 instead of 2007?
> >> >
> >> >> When I was asking about ActiveX, I was asking about controls on the
> >> >> form's
> >> >> design surface, not the code behind the form. You're not using any of
> >> >> the
> >> >> new controls that come with Outlook 2007, are you?
> >> >
> >> >> "BuddyWork" <BuddyWork> wrote in message
> >> >> news:35B1C691-9110-4BE9-95D0-69246C788205@microsoft.com...
> >> >> > Its a custom meeting form IPM.Appointment.
> >> >> >> >> > "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?
> >> >> >
> >> >> >> "BuddyWork" <BuddyWork> wrote in message
> >> >> >> news:CD9FF8BA-1F77-4943-9D58-ABC24CAABCBF@microsoft.com...
> >> >> >> > 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" <BuddyWork> wrote in
> >> >> >> >> message
> >> >> >> >> news:CD3C6C26-7D2F-4657-B77B-C7E3A1D2BB0F@microsoft.com...
> >> >> >> >> >> >> >> >> > 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.
> >> >
> >> >
> >> >
> >
> >
> >>


>
 
Status
Not open for further replies.
Top