Answer 1

Hi,

What about creating a Custom List Definition? You can control the fields, content types, views of your list and the forms used to interact with a single item.

Here you will find general information about creating a custom list definition : http://msdn.microsoft.com/en-us/library/ms466023(v=office.12).aspx You have to create a schema for your list. In this schema you can specify the files to use as forms for interacting with a single item (Display, Edit and New form).

Information about the schema and the Forms element : http://msdn.microsoft.com/en-us/library/ms459356(v=office.12).aspx

Hope it will help you.

Answer 2

Hi VBCoder60,

What pages  were modified?

If they were specific to the list in question and modified using SPD 2007 (NewForm.aspx, DispForm.aspx, EditForm.aspx) try to save the list as a template (in List Settings -> Save list as template).  Don't include content unless you need to move all the existing list items.

Go to the List Template Library and download your list template (.stp file)

Upload it to your test environment's List Template Library.  Then try to create a new list using that template and see what functionality is missing (if any).

Does this meet your needs?

-Xenox G.

Answer 3

Thanks for the two replys on identifying a solution for deploying customized  forms from one site to another.  I have read over both solutions but I don't think they are an ideal fit.  Mainly because the list in question already exist on the target site.  If the list did not exist on the target site then either method would work. 

So I am still in search of a solution that would allow me to deploy  customized pages  to an existing list in the target site.  These are standard pages (NewForm.aspx, EditForm.aspx, DispForm.aspx) that were created when the list was created using existing templates.  After the list was created these pages were customized to provide additional utility.  This means that these pages already exist in target site as customized pages.  The method used by the previous programmer was not documented so it is unknown to me.  I would like to deploy the latest version (with more customizations) to the target site without breaking the existing list or loosing any of the content. 

I would appreciate inputs on this.

Answer 4

Thanks for the two replys on identifying a solution for deploying customized  forms from one site to another.  I have read over both solutions but I don't think they are an ideal fit.  Mainly because the list in question already exist on the target site.  If the list did not exist on the target site then either method would work. 

So I am still in search of a solution that would allow me to deploy  customized pages  to an existing list in the target site.  These are standard pages (NewForm.aspx, EditForm.aspx, DispForm.aspx) that were created when the list was created using existing templates.  After the list was created these pages were customized to provide additional utility.  This means that these pages already exist in target site as customized pages.  The method used by the previous programmer was not documented so it is unknown to me.  I would like to deploy the latest version (with more customizations) to the target site without breaking the existing list or loosing any of the content. 

I would appreciate inputs on this.

If your production list already exists, I would do the following to test functionality.

Save your existing list as a list template including content from your production site.

Put the list template in your development environment and create a list from this template for testing.

Replace the newform.aspx/dispform.aspx/editform.aspx forms on this test list with your custom modified forms using Sharepoint designer 2007 which lets you choose custom forms for lists (Right click on the List name and click List Properties -> Supporting Files Tab).  Test the functionality on your development environment.  If it all works properly, you can re-templatize the list and move it back to production.

Keep in mind that you will want to test this in your dev environment thoroughly.

-Xenox G.