Yes, that's how its supposed to work, I entirely agree. But my user's problem
is that Outlook is not functioning as expected. For existing items it only
looks in the local cache, andthrows up an error if it can't find the form
there. Also, it doesn't check if there is a newer version of the form in the
Organizational Library, always using the local cached version of the form if
there is one. This means that if form names are changed when the forms are
updated my user won't be able to use the new form for either new or existing
items?

Any ideas??

Thanks

Vaughan


"Hollis D. Paul" wrote:

In article ,
=?Utf-8?B?VmF1Z2hhbg==?= wrote:
I don't think that changing the form name would help in this case though?
The problem is that Outlook does not look beyond the local cache.

If it is a new form name, it has to look beyond the local cache.

Hollis D. Paul [MVP - Outlook]
Mukilteo, WA USA