New Version of a Custom Form

[Jerry Camel]

Got a custom form attached to a public folder. Only form that can be used
for posting.
There are several items in the folder that are successfully using the form.
I update the form with a new field. And incremented the version number.
How do I get the existing items to use the new version of the form?
I tried DocMessageClass, but it won't update items to a form with the same
message class.
I tried converting the items back to the default and then to the custom
form, but they still use the old version of the form. I even tried clearing
the forms cache...

Any thoughts? Thanks.

Jerry

 

[Hollis D. Paul]

I tried converting the items back to the default and then to the custom
form, but they still use the old version of the form. I even tried clearing
the forms cache...

The only way to coerce the forms manager to keep track of the versions of
forms properly is to include the version indicator in the published name of
the form. So, if you have a form originally published as Postem, then you
want to publish the first revision version as Postem_1. Then, when you use
the utility, found on www.slipstick.com among other places, to change the
MessageClass field of the form, to Postem_1, you will get the old items
displayed with the new form. If you just change the Version Number field, but
leave the name as Postem, you can get the problems you are experiencing.

Hollis D. Paul [MVP - Outlook]
(e-mail address removed)
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US

Mukilteo, WA USA

 

[Jerry Camel]

I was trying to avoid having to publish new message classes every time. If
that's what it takes then that's what it takes... But this time, it seems
it was just timing. As of this morning, the new version of the form has
kicked in. I just didn't wait long enough, I guess. I figured if I cleared
the forms cache, it would have to download the new version...

Since the form is attached to a public foler, rather than the org forms lib,
could this be a public folder replication issue?

I tried converting the items back to the default and then to the custom
form, but they still use the old version of the form. I even tried clearing
the forms cache...

The only way to coerce the forms manager to keep track of the versions of
forms properly is to include the version indicator in the published name of
the form. So, if you have a form originally published as Postem, then you
want to publish the first revision version as Postem_1. Then, when you use
the utility, found on www.slipstick.com among other places, to change the
MessageClass field of the form, to Postem_1, you will get the old items
displayed with the new form. If you just change the Version Number field, but
leave the name as Postem, you can get the problems you are experiencing.

Hollis D. Paul [MVP - Outlook]
(e-mail address removed)
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US

Mukilteo, WA USA

 

[Hollis D. Paul]

Since the form is attached to a public foler, rather than the org forms lib,
could this be a public folder replication issue?

I supposed it might be. When looking to find the form, it looks first at the
Org Forms Library. After that, I am not sure of the order.

You really need to get over the fear of putting two many forms in the Org
Forms Library. When the clutter gets too much, you delete the old ones.
However, you probably do have to reset the new form as the default form for
the folder. Small price to pay for getting the forms to work every time, all
the time.

Hollis D. Paul [MVP - Outlook]
(e-mail address removed)
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com/kb/c.asp?FR=0&SD=TECH&LN=EN-US

Mukilteo, WA USA