Outlook Custom Form Problem

[ropio]

I have a custom outlook form in Outlook 2003 that was working fine. I'm not
sure what changed but some users are having the following problem.

They read the custome form, close it and it they go back to reread the form
I get scripting errors.

The errors are on different lines in the script in our test environment and
our production environment. So it is not failing at the same line of code.

Has anyone had a problem like this - or where can I go to research it

 

[Ken Slovak - [MVP - Outlook]]

You can go to www.outlookcode.com and search on something like "form
errors". Without knowing what type of errors are being fired and if they are
consistent errors it's really impossible to know what's going on or why.

You can also check to make sure that the forms aren't one-offed or corrupted
in some way. But I don't think that's the case with your problem.

 

[ropio]

On the production form I'm getting Script Error Operation Failed at line # 3217
Here's that line
Set DetailPage = Item.GetInspector.ModifiedFormPages("Requisition Detail")

On the test form I get Error Object Required "Attach Page" at line 1841
Set MultiPage1 = AttachPage.controls("MultiPage1") - there is no attachment
for this form

I donot get any errors on my machine, I can get into the form open and close
it and re-read it as many times as I like. Can the fact that I am a
developer and have certain permissions allow me to re-read the form. Can it
be a security.

Can it be a patch was installed that could create this?

Also if the form is corrupt, how do I fix that.

thanks in advacne fro your help

 

[Ken Slovak - [MVP - Outlook]]

I don't see permissions or security being an issue, unless the form is
published in a restricted folder.

If a form is corrupted then about all you can do is to remove the form and
clear the forms cache in the forms manager and republish it. If forms are
one-offed the typical symptom is that it increases in size due to the form
description being embedded in the form rather than being pulled from the
cache or library. You can compare item sizes for various forms and see if
some are much larger than others.

For those errors it could be that the form is one-offed, but usually those
forms won't run code, or that the item isn't opening to the correct form. In
that case those controls and ModifiedFormPages won't be there. That can be
checked by checking the MessageClass of the item in the Load() event. If
code has to run based on reading an email from the preview pane you can also
check in Read() for MessageClass.

One workaround that some of us use is to actually set the MessageClass if
it's not correct, so that the form is always used for that type of item. But
that requires that all items of that type use that custom form, at minimum
at least in certain specific folders that can be identified.

 

[ropio]

Some users are putting the form in a folder they created. Is that where I set
the Message Class and if so, how do I do that.

Some users just have it in there Inbox so I don't think that would work there.

Correct me if Im wrong

thanks again for your help

 

[Ken Slovak - [MVP - Outlook]]

It doesn't matter where the item is as long as it's published in the
Personal Forms Library or the Organizational Forms Library. The custom
MessageClass will be available. If the form is published to a folder it will
only be available in that one folder. One thing that you must avoid is
publishing a form in more than one place.

To check/set the MessageClass is simple. Say the form is an email form, the
default MessageClass is "IPM.Note". A custom form might be
"IPM.Note.MyForm".

To check/set the MessageClass:

If Item.MessageClass = "IPM.Note.MyForm" Then
'OK
Else
Item.MessageClass = "IPM.Note.MyForm"
EndIf

 

[ropio]

I added that code and it didn't help. I stepped throught the code and one
thing I noticed on my PC (the one where everything is fine, I can read and
reread the item as many times as I like) item_read and item_open always fires

On the users machine the first time they read it both fire, when they
re-read it only item_open fires -- Is that expected behavior?

Also, on the users machine if they read the message and then clode outlook
and start it again they can re-read the message.

 

[Ken Slovak - [MVP - Outlook]]

That sounds like something isn't being released, what I have no idea.
Normally you get Read() as often as it gets focus and is opened or being
read in the preview pane. You only get Open() when an item is opened, so I'd
expect if it was still in memory that you wouldn't get Open() again but you
would get Read().

It might be corrupted forms or a bad forms cache. Beyond that I'm at a loss
about what's going on. Did you check the item sizes where it's happening and
where it's not? When it happens, does it happen for every item on that
Outlook, or only on certain items? Do all the items, where it's working and
where it's not, have the same form version?

If this is only a few users and it works OK everywhere else I'd just clean
up their systems and forms cache, unpublish the form, and start over with a
clean installation.

Otherwise it's just a lot of step by step troubleshooting.