Re: publishing customized contact form on server

In article <1CA8E25F-4798-4F67-A870-8C312B448F37@microsoft.com>,
=?Utf-8?B?SW5kdQ==?= wrote:
> I have a customized contact form published to a folder in public folder, I
> was wondering if it is possible to replace the default contact form to
> customized form on the server so that whenever new contact is enter the
> customized form is loaded as the custsomized contact will be used by all
> employees restricting them to use the default form. If this is possible
> what kind of problems I could run into? Will this restrict me from making
> changes to the form? We have Window Server 2003 Enterprise Edition.
>
First, you want to publish the form to the Exchange Forms Library. This will
make the form available to everybody, and is the first place the system looks
for a form.

Second, go to www.slipstick.com and search on default. One of the hits in
the results set will tell you how to make that form your new default form,
and then, as this will be your next question, how to change all the data
items that display in the old form so that they display in the new form. I
am not sure, but I think that this will have to be done on each of the client
machines that will be using this form.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com...D=TECH&LN=EN-US

Mukilteo, WA USA

Hi Hollis;

Thank you for your reply, but I was wondering what kind of problems I can
face when publishing the customized form to the exchange forms library. I
often end up makeing changes to the form....what kind of problems this can
cause?

Thanks


"Hollis D. Paul" wrote:

> In article <1CA8E25F-4798-4F67-A870-8C312B448F37@microsoft.com>,
> =?Utf-8?B?SW5kdQ==?= wrote:
> > I have a customized contact form published to a folder in public folder, I
> > was wondering if it is possible to replace the default contact form to
> > customized form on the server so that whenever new contact is enter the
> > customized form is loaded as the custsomized contact will be used by all
> > employees restricting them to use the default form. If this is possible
> > what kind of problems I could run into? Will this restrict me from making
> > changes to the form? We have Window Server 2003 Enterprise Edition.
> >
> First, you want to publish the form to the Exchange Forms Library. This will
> make the form available to everybody, and is the first place the system looks
> for a form.
>
> Second, go to www.slipstick.com and search on default. One of the hits in
> the results set will tell you how to make that form your new default form,
> and then, as this will be your next question, how to change all the data
> items that display in the old form so that they display in the new form. I
> am not sure, but I think that this will have to be done on each of the client
> machines that will be using this form.
>
> Hollis D. Paul [MVP - Outlook]
> Hollis@outhousebythesound.com
> Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
> http://search.support.microsoft.com...D=TECH&LN=EN-US
>
> Mukilteo, WA USA
>
>
>

In article <4224229B-2401-4E36-B079-6E8E3F45782D@microsoft.com>,
=?Utf-8?B?SW5kdQ==?= wrote:
> Thank you for your reply, but I was wondering what kind of problems I can
> face when publishing the customized form to the exchange forms library. I
> often end up makeing changes to the form....what kind of problems this can
> cause?
>
No problems if you include the version number in the name of the
form--OurContacts_Ver6. If you republish using the same name, then you can
have forms cache problems, because the system cannot always tell that a new
version of the form has been created, It will work properly most of the
time, and then you will be thrown into a panic because it doesn't at some
point and you haven't done anything different.

You will, however, need to use the forms manager to reduce the number of
forms that appear on the list when users go to retrieve it. My
recommendation is to keep a .pst file for the purpose of keeping at least
three generations of the form available--lack Son, Father, and .... That
way, you are sure go have a good copy of the last working version when some
new change one-offs the form. You don't want to start from ground-zero in
the reconstruction.

Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Using Virtual Access 4.52 build 277 (32-bit), Windows 2000 build 2600
http://search.support.microsoft.com...D=TECH&LN=EN-US

Mukilteo, WA USA