SharePoint University

Hi All,

UPDATE

 Apparently Microsoft knows about this issue and is working on a hotfix.  Right now there is no workaround so that folder will have to sit out on my production site like an ugly wart. 

I am having the same exact issue for the same exact reasons.

I was trying to create a template file which is a Microsoft Excel 2003 document and created a directory named "Forms" (thinking since it was a form that we use) and I was going to attempt to assign this form as the template for that directory.

 I have found a number of issues with this:

1.  "Form" is reserved for WSS (that's what we use).  There is no stopping from anyone creating this, but you sure aren't ever going to delete it!
2. You cannot create a template for a specific directory, only for the entire "Document Library" which means even those subdirectories use the same template.  (I use the term directory because of our old DOS days, and I hate the term "Folder).
3. You are limited to only one template in a document library, but isn't a "LIBRARY" supposed to contain many different types of information?  Since when have you gone to a library and only seen magazines but not books???  Or books but no shelves for them to be organized on?

Microsoft is really limiting business to their standards and I really wish we could "stretch our arms" or at least organize the way the company has been for the past 19 years, which I must say, seems better than conforming to Microsoft's version of business.  (Watch "Pirates of Silicon Valley")

2. Folders are not a physical structure, only a logical one for organization of documents. They are a simple content type. Folders don't allow you to create documents as they are only a form of laying out yoru library, the library is what creates the documents so the template is at the library level.

 3. You are not limited to one template for a library. You should really look into Content Types. Content Types allow you to specify a template. So you can create as many content types as you want. Name them some logical. Associate a document template with them. Then turn on the manage content types setting in your document library. You should then be able to associate your content types with the library. Once you have done this, any time a user hits the "New" drop down for the library, they will get options for each content type you created, that means any template you have assigned to the content types is not available on the dropdown.

 Part of limiting what can be done in a product is identifying what you can realistically support. It is hard to say do anything at all under the sun and we will magically be able to fix it if you break it. But that's just my opinion of course, I am biased...

BluePhaze: 

I have to admit that I was extreme on the emotional outburst of my post, but I had to vent.  It boggles my mind that a product so highly regarded and seemingly invaluable would have such intimidating issues.  If I were to be working in an environment with developers or equivalent, I could easily be fine with the "don't name folders this..." approach, but I have to deploy a solution that our company has committed to SharePoint with, and every employee that is not in IT here is an "over-educated idiot" (according to my boss) 

I appreciate your response and I will try to develop a solution that we can be happy with.  Unfortunately, your (most appreciated) solution to #3 is not acceptable from our standpoint because of certain HR functions and organizational planning.  Basically, our HR people seemed to have used computers in the future that do exactly what they want and nothing bad has ever happened to any of their documents ever before and do not understand why the same file names have different "icons" because this was never an issue at any other employer they have worked at.

I think they're just high, or they had some amazing IT guys that were always fixing their mistakes without them knowing they made any.

When I find out how to get rid of this "Forms" directory, I will re-post.

 I have the same problem...has anyone found a fix yet?

Nope.  I am in fact STILL dealing with it.  I have since deleted and re-created the entire web site (thankfully it became just a testbed)

 Wow.  Unfortuately, I've got a rather large document libaray, with each sub folder containg a "Forms" folder.  I don't really want to recreate it.  Hum, strange...who would have thought you couldn't use Forms as a folder name!

The "Forms" folder is a hidden/secret folder that the system uses for itself.  You may be able to remove your ghost folder with SharePoint Designer.  If this is a fairly new Document Library, then it is fairly easy to Actions-->Open with Windows Explorer, drag and drop a copy of all of your content to a network folder, delete the document library, create a new document library, Open with Windows Explorer again, and then drag and drop the entire contents back into the new Document Library.  Via Explorer view you might be able to deal with your ghost folder also - haven't tried.

 I just named my folder "All Forms" as a workaround.  Anything but "Forms" should work.

FDB1:  I tried doing that.  I would browse to the UNC path of my server and it began doing some REALLY WEIRD stuff.  The problem is that the site actually uses the hidden "Forms" folder which then becomes a trial and tribulation to deal with.  In fact, I remember using this sentence: "YOU MOTHER$*@#ER PIECE OF $#*& JUST WORK!"

Anywho.  I dare you to try it yourself.  Create a folder named "Forms" and watch the havoc wreak! (Pay close attention to my original post(s) as I have explained exactly what I did - I started this thread, so it's easy to find.)

Oh, and SharePoint Designer didn't help anything.  A valueable and necessary tool to have, but still not helpful in this particular situation.

The more deeply I get to know Sharepoint the more I wonder a) what internal politics resulted in Sharepoint's team rethinking the tried and tested ntfs filesystem which is both fast and easy to backup and restore, and b) why so many people find it an amazing product when it exhibits so many annoyances that the every day user can easily stumble across.

It stuns me that they would include a feature that requires protection of extremely commonly used labels (Forms and Attachments - could there be more) and wouldn't bother to write a procedure which prevents users creating objects with these names.  If they had use something more obscure (one wonders if they had ever heard of a naming convention) like "_Forms" then they wouldn't be frustrating anyone!

</rant>

I'm also stunned that my organisation bought into this hook line and sinker and that I didn't kick and scream as I was put in charge of the system...

THere has to be a way to use an html editor just to remove the referance to the content.!!!?

Nope-  I had this problem too... I named another folder Forrns in a feeble attempt to trick peoples' eyes.