If I create a new list, any new list, I see that I have the columns Title, Created By, and Modified By. When I click new on the list to add something, I see Title and Title. Yes, I see it twice. If I click on the Title that is listed under _layouts/ListEdit.aspx?List=xxxx, I can actually delete that column. That isn't right. In addition, the end of the URL shows "Field=AVMTitle". I can see the true Title that one isn't supposed to be able to delete by changing it to "Field=Title". How do I fix this? The Title column that should come up under _layouts/ListEdit.aspx?List=xxxx isn't there. I'm thinking about replacing the definition of Title in the ContentTypes table of the SQL DB with another site collection's definition, but that scares me.

Hello, Did you create a list from the available list types we get in sharepoint or did you create it from some other webpart?Thanks & Regards, Chandra Shekhar Rameneni

That almost sounds like the Item content type was edited, and then the changes were propogated all the way down? Have you checked what the Item content type looks at at the site collection level?- Michael Mukalian - 2010 MS MVP SharePoint Services - MCTS: MOSS 2007 Configuration - http://www.mukalian.com/blog

I believe it got edited in the actual SQL table after talking with the guy responsible. Now I need to clean it up. When you look for this under content types and try to edit the column name Title, it is in the Absence and Vacation Schedule Fields group instead of _Hidden. I changed it to _Hidden, but that doesn't help. The URL for it is http://xxxxx/_layouts/FldEdit.aspx?CloseOnCancel=1&Field=AVMTitle. I know that AVM shouldn't be there. I think I have a dozen or more places to manually change this back in the SQL DB and risk it all going to hell. My other option would be to manually attempt to move all of the content over to a new web application by saving the lists and sites as templates with content and uploading them into the web application. This will be a lot of work, one way or another.

Careful there...MS views fooling around directly with the database as a no-no. I'd go with the migration to a new web app route, into a "clean" database, that way you're back in a supported scenario. You should never, never mess with the database directly at any time. - M- Michael Mukalian - 2010 MS MVP SharePoint Services - MCTS: MOSS 2007 Configuration - http://www.mukalian.com/blog

I know. Luckily, there isn't a lot of content, but there are lots of sites. Any suggestions on how to move it the easiest? I was going to save sites with content and put them in the the new web app.