Shared Form

[Joel Allen]

Hello,

I have tasks on my local Mailbox.
I open the task and edit some fields.
Save and close.
Open the form.
No failure.
Task is not currupt.

My coworkers open the task by going through my mailbox which I have shared.
(I gave them full owner rights. I also cleared cache on all their
computers.)
It is corrupt.

From my computer, it is still Not Corrupt. Also, I have logged onto my
cooworkers computer as myself. I can open the task and it is not corrupt.

I have proven that the task itself is not currupt, but there is something
preventing my coworkers from opening it!

What do you think?

-Joel

 

[Sue Mosher [MVP-Outlook]]

Define "corrupt," please.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Joel]

Of course. Please let me be more specific:

When my coworkers open the task from their computer, they get an error that
says the form cannot open and it will use a another form instead. I Click
OK. Then it says it cannot open the form. When you right click on the
task, you don't get any properties. I cannot copy or move it.

Yet - from my computer, I can open it fine. When I am logged on my
coworkers computer under my username, it works fine too.

Thanks for your help,
Joel

Define "corrupt," please.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Is the form published in the tasks folder? Have you tried clearing the forms cache for the affected users?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Joel Allen]

The form resides on my Mailbox, not in the public area. I share it out to
users. I have cleared Cache on everybodys computer.

-Joel

Is the form published in the tasks folder? Have you tried clearing the forms
cache for the affected users?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

That doesn't really tell us what might be a critical factor -- where is the form published that is supposed to be used by these items?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Joel Allen]

It is published to a folder on my Mailbox called Outlook:\\PMS

Does this help?

-Joel

That doesn't really tell us what might be a critical factor -- where is the
form published that is supposed to be used by these items?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

And do the tasks that your coworkers are opening reside in that same folder?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Joel Allen]

Yes, they are opening the same task because they are going into my shared
folder in my Mailbox.

And do the tasks that your coworkers are opening reside in that same folder?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

What I was trying to ascertain was whether the form was published in the same folder that stores the items. Now that we know that it is, we know that the items should open in that form. The one thing you may not be aware of, though, is that those forms will not run code unless you set a particular registry value for each user besides yourself; see http://www.outlookcode.com/d/ol2003problems.htm

The symptoms are those of forms cache corruption. In addition to clearing the cache through the UI, I'd suggest that you delete the entire contents of the Forms folder where the frmcache.dat file resides.

Also, what version and build number of Outlook is this?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Joel Allen]

I do have the box check checked that allows the script in shared folders.
I have cleared the cache and deleted the frmcache.dat file and form folder.

I am running Outlook 2003 SP1.

Thanks,
-Joel




What I was trying to ascertain was whether the form was published in the
same folder that stores the items. Now that we know that it is, we know that
the items should open in that form. The one thing you may not be aware of,
though, is that those forms will not run code unless you set a particular
registry value for each user besides yourself; see
http://www.outlookcode.com/d/ol2003problems.htm

The symptoms are those of forms cache corruption. In addition to clearing
the cache through the UI, I'd suggest that you delete the entire contents of
the Forms folder where the frmcache.dat file resides.

Also, what version and build number of Outlook is this?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Hmm. Does this affect all users or just some? Do they have a similar problem if they try to create new items in the folder?

You might to try the ForceFormReload registry value described at http://support.microsoft.com/default.aspx?scid=kb;en-us;839804. That article has other troubleshooting steps as well.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Joel Allen]

It happens to all users. They do have similiar problems on new items, but
it's hit and miss.

-Joel

Hmm. Does this affect all users or just some? Do they have a similar problem
if they try to create new items in the folder?

You might to try the ForceFormReload registry value described at
http://support.microsoft.com/default.aspx?scid=kb;en-us;839804. That article
has other troubleshooting steps as well.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Did you try ForceFormReload? Did you try incrementing the version number of republishing the form?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Joel Allen]

I'll republish and reincrement. How do you ForceFormReload?

Did you try ForceFormReload? Did you try incrementing the version number of
republishing the form?

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

Read the KB article I suggested two posts ago.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Joel Allen]

I'm sorry Sue, I cannot find the article you are pointing to in two post
ago. Can you provide a link?

Read the KB article I suggested two posts ago.

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Sue Mosher [MVP-Outlook]]

I did provide a link, which you can read below. And here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;839804

--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003

and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers