Outlook doesn't recognize some of the script

[Alami. M]

I have experiencing this case with one of my frinds
machine. I have a form that has a script, I discover that
outlook doesn't recognize some of the script, for example :
- The 'VbYes' constant
- script doesn't stop at 'stop' statement
- 'ObjItem.save' doesn't work and no error reported
- If I run my form and go to Tools/forms/ Script
Debugger . Nothing happen, no scrip debugger !!.

He is using Outlook 2000 SP3.
Does anybody have any idea?. Thanks

 

[Sue Mosher [MVP]]

There are two major causes of code in an Outlook form not running -- 1)
security settings in Outlook 2003 and 2) the broader form script security
features introduced with the Outlook Email Security Update.

#1: Outlook 2003 includes a new setting -- turned off by default -- to allow
forms in shared mailboxes to run script. You can change the setting by
choosing Tools | Options | Other | Advanced Options and checking the box for
Allow script in shared folders. See
http://www.slipstick.com/dev/ol2003problems.htm#mailboxscript for more
information on this setting and a comparable one (on by default for public
folders).

#2: If the form runs code when you use Run This Form in design mode, but
doesn't run code after you have sent or saved an item using the form, you
probably have done something to "one-off" the form. Outlook 2003, Outlook
2002, Outlook 2000 SP2 and Outlook 2000 or 98 with the Email Security Update
will not run code on one-off forms; see
http://www.slipstick.com/outlook/esecup.htm#formsec for more information on
this issue.

To ensure that a form does not one-off:

-- Make sure the "Send form definition with item" box on the (Properties)
tab of the form is *not* checked. [1]

-- For in-house corporate use with Exchange Server, publish the form to the
Organization Forms library or a public folder's forms library, as
appropriate for your application.

-- For collaboration via the Internet, publish your form to your Personal
Forms library. Save it as an .oft file and send it to other people who need
to use it with instructions to publish it with the same form name that you
used.

Many other things can cause one-off forms. If the above steps don't work on
a new item created with your form, see
http://www.slipstick.com/dev/formpub.htm#oneoff for other possible causes.

[1] Whenever you publish a message form, Outlook will suggest that you may
want to check the "Send form definition with item" box to ensure that the
recipient will have the form, especially if you're sending to someone via
the Internet. In the current Outlook security environment, this suggestion
is obsolete. Ignore it unless your form has no code behind it.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Alami. M]

Thanks sue Mosher for the info.
But my form is not One-Off because other script functions
are working fine in the same form.
This is the part of the script I'm getting problem with:
'''''''''''''''''''''''''''''''''''''''''''''''''''''
If blnMsgResponse = VBYES then
'I had to change 'vbyes' to 6 in order to pass
For each objItem in oResItems
If ObjItem <> Item then
ObjItem.OrganizationalIDNumber =
Item.OrganizationalIDNumber
ObjItem.Save
'Save seems to cancel !!
End If
Next
End If
'''''''''''''''''''''''''''''''''''''''''''''''''''''

I did never see this problem before!!!

-----Original Message-----
There are two major causes of code in an Outlook form not running -- 1)
security settings in Outlook 2003 and 2) the broader form script security
features introduced with the Outlook Email Security Update.

#1: Outlook 2003 includes a new setting -- turned off by default -- to allow
forms in shared mailboxes to run script. You can change the setting by
choosing Tools | Options | Other | Advanced Options and checking the box for
Allow script in shared folders. See
http://www.slipstick.com/dev/ol2003problems.htm#mailboxscr ipt for more
information on this setting and a comparable one (on by default for public
folders).

#2: If the form runs code when you use Run This Form in design mode, but
doesn't run code after you have sent or saved an item using the form, you
probably have done something to "one-off" the form. Outlook 2003, Outlook
2002, Outlook 2000 SP2 and Outlook 2000 or 98 with the Email Security Update
will not run code on one-off forms; see
http://www.slipstick.com/outlook/esecup.htm#formsec for more information on
this issue.

To ensure that a form does not one-off:

-- Make sure the "Send form definition with item" box on the (Properties)
tab of the form is *not* checked. [1]

-- For in-house corporate use with Exchange Server, publish the form to the
Organization Forms library or a public folder's forms library, as
appropriate for your application.

-- For collaboration via the Internet, publish your form to your Personal
Forms library. Save it as an .oft file and send it to other people who need
to use it with instructions to publish it with the same form name that you
used.

Many other things can cause one-off forms. If the above steps don't work on
a new item created with your form, see
http://www.slipstick.com/dev/formpub.htm#oneoff for other possible causes.

[1] Whenever you publish a message form, Outlook will suggest that you may
want to check the "Send form definition with item" box to ensure that the
recipient will have the form, especially if you're sending to someone via
the Internet. In the current Outlook security environment, this suggestion
is obsolete. Ignore it unless your form has no code behind it.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

I have experiencing this case with one of my frinds
machine. I have a form that has a script, I discover that
outlook doesn't recognize some of the script, for example :
- The 'VbYes' constant
- script doesn't stop at 'stop' statement
- 'ObjItem.save' doesn't work and no error reported
- If I run my form and go to Tools/forms/ Script
Debugger . Nothing happen, no scrip debugger !!.

He is using Outlook 2000 SP3.
Does anybody have any idea?. Thanks

.

 

[Sue Mosher [MVP]]

There's no obvious reason why part of the script would run and part
wouldn't, assuming it's all valid code. Since you're using Outlook 2003, I
would suspect forms cache corruption and clear the cache. Also, if you have
an On Error Resume Next statement, comment it out to see if you get any
errors.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Alami. M]

as I said this is happen for outlook 2000 SP3 . also the
form works fine in my site, but not in my friend !!

 

[Sue Mosher [MVP]]

Sorry I misread the version. I'd still try clearing the forms cache.

 

[Jim VanHook]

Alami -
The script engine is independent of Outlook itself. It's possible that your
friend doesn't have a version of the engine that supports named constants.
Check the version of VBScript.dll in the System32 directory and compare
between the two systems. While it seems unlikely an old version is still
around, your description of the symptoms would seem to indicate that's
what's going on.

- jim

 

[Alami. M]

vbscript.dll seems to be a new version 5.6.0.7426.
I recognize that this happen to all their outlook
wokstations.
I recognize that in outlook help box, they have after
outlook version the following sentence:
"Corporate or workgroup - Security Update"
I recognize also that they are installing 'SpamNet'
software against spams.

My questions:
Could be their any setting in Exchange server that cause
this?
Can Spam softwares cause this?
I appreciate all helps, thanks