I am looking for a solution to link the title column to the document in a document library. any solutions available. Please help!

Why do you need this ? The Name column is always there and it already links to the document as does the icon.FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com Complete Book Lists (incl. foreign language) on each site.

I agree with Mike why take this approach if Name is already linked? Maybe you can provide the actual business reason for it and then we can provide an alternative approach. With that being said you can use a content query web part, edit the XSLT to link the title column to the document in the document library and display this view in a separate page. This will not change the List View page or the actual column names but rather provides the business (if that's where the request is coming from) a different view of the data. p.s. Be very cautious when renaming or manipulating out of box columns given to you in a document library.

Here is an example of where it would be nice to have this working: Quotes document library. Quotes will often arrive without freindly names 20010101XYZ.pdf, so you can add a column called "quote name" and see a friendly name such as "Contoso Quote", then having the Type icon linked to docuement. Problems is that the icon does not seem to link to open document? The thing that I'm sure you will point out is why not rename the document? This would be a fine solution, but will not currently work as you cant rename "Name" to "Quote Name" or add a description? any thoughts? or other options?

The correct answer to the original question is that it can't be directly done, or someone is afraid to address that. Mike and Kanwal: it's a bit obnoxious to immediately respond to a person's question with "Why would you do X?" when it has nothing to do with solving the problem. The poster clearly has a reason for asking the question to begin with. Personally I've had the same question in mind. It's for readability. Filenames shouldn't have special characters, spaces etc. Thus, it's better to use the title when you display a link. Think of any web link: you don't show a user "termsOfUse.html".. you show them "Terms of Use". All that said, Kanwal does provide a possible solution to the dilemma. A Data View Web Part will also handle this, but it takes a little more than a couple of clicks to get going.

>Mike and Kanwal: it's a bit obnoxious to immediately respond to a person's question with "Why >would you do X?" when it has nothing to do with solving the problem. The poster clearly has a >reason for asking the question to begin with. This sort of personal attack is completely unnecessary. Neither Kanwal nor myself were at all "obnoxious" in our *on topic* replies. It is reasonable to ask why something odd is being asked when there already is a built-in solution to the problem. Perhaps the poster isn't aware of the built-in solution and in any case asking why he wants to do this helps the forum members to later provide an answer (if one exists). P.S. This appears to be your first forum post. Perhaps you should spend some time in the forums before attacking anybody. Both Kanwal and myself have provided lots of answers to problems in the forums as can be seen by our respective points scores. 2010 Books: SPF 2010; SPS 2010; SPD 2010; InfoPath 2010; Workflow etc. 2007 Books: WSS 3.0; MOSS 2007; SPD 2007; InfoPath 2007; PerformancePoint; SSRS; Workflow Both lists also include books in French; German; Spanish with even more languages in the 2007 list.