> It's your choice whether to publish to the Organizational Forms library once or to each individual's Personal Forms library. I know which one I'd find easier to maintain.
>
[quoted text clipped - 52 lines]
> >> >
> >> > InnoTech, Inc.
> Are there some articles describing best practices regarding publishing of
> custom forms to public folders and having them accessible to saved items?
No, because saved items -- as in .msg files -- cannot access forms published in public folders. Any form for use by an .msg file must be in Org Forms or Personal Forms.
> To be honest I'm not too sure about the whole One-Off concept. When the
> Work Ticket items are saved, the form definition is _not_ saved with them.
> I've read elsewhere that this is bad.
No, it's generally good. There are few scenarios in which saving the form definition with the item is appropriate.
> I've read a couple knowledgebase
> articels on the one-off concept and believe that I'm not creating one-off
> items, but I'm not sure.
You can check the value of the MessageClass property using Outlook Spy or by writing VBA code to get the value of Application.ActiveInspector.CurrentItem.MessageClass when the item is open. One-off items are also larger than regular items because of the embedded form they contain.

Signature
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
> Yes, the custom forms are based on the same message class. I forget the
> exact custom form class, but I believe it is something like
[quoted text clipped - 7 lines]
>>
>> Does "older ones that were saved with a previous versoin" mean published with a different message class? Are these one-off form items?
>> > Sue,
>> > Thanks for the quick reply.
[quoted text clipped - 48 lines]
>> >> >
>> >> > InnoTech, Inc.