You know, I never cease to be amazed at how smart people get stuck in ruts (myself included).

I was a WordStar user in the '80's. Correction - power user. I knew all the dot commands, advanced commands, could make WordStar sing like the devil's own fiddle. However, I started hearing about this new "high end" word processing application everyone was using called WordPerfect. Of course, being the power geek I am, I had to try it out. I got an educational version of WordPerfect 5.1 and eagerly installed it.

C:\ > cd WP51

C:\WP51\ > WP

Got a splash screen, then some numbers in the lower right hand corner and a blank screen. Waited.... Waited....

Oh, I guess this is it. What the heck? This sucks! How do I format stuff? How do I set up indentation? HOW DO I GET OUT OF HERE?!?!? etc, etc, etc...

Grudgingly, I picked up the manual and started reading. And learned about F-keys. (now all the geezers are nodding sagely and mumbling f-key combinations under their breath).

WP used a different paradigm, and it took getting used to. Of course, the constant barrage of "Why doesn't Word have reveal codes?" indicates that a lot of people took the time to get used to it. [grin]

Which brings me back to my subject line. Why doesn't SharePoint have a treeview?

The reason SharePoint doesn't have a treeview is that SharePoint doesn't work that way. SharePoint, in fact, is the antithesis of the treeview. Treeviews are sharp definitions of the hierarchical nature of a website. HQ at the top, then division heads, departments, etc, etc. The problem is that unless you're submitting your employee performance appraisal, almost nothing that you do works that way.

Vacation requests to go HR.

Accident reports go to the safety office.

Expense reports go to your accounting person, then to your boss, then to finance.

Transfer requests have to be approved by the HR person in the department you want to transfer to...

Stuff that you do in your day job is functional, and depends on the task at hand, not who you work for. SharePoint is an attempt to provide ways for people in the organization to find what they're looking for. Windows SharePoint Services team sites provide collaboration within the working group that you're a participant it. It's primarily link-driven because these groups are generally invitation-driven. (You don't go wandering around the office randomly opening doors to see if there are interesting meetings going on. I mean, I do, but that's different...)

SharePoint Portal Server enters the picture when you start talking about sharing information outside the workgroups - it provides areas to publish information for internal consumption, Topics to provide ways to aggregate that information, uh, topically instead of hierarchically, and enterprise search capabilities because, when it all comes down to it - we search for what we're looking for.

That's why a treeview in SharePoint isn't such a huge deal. But we love our dot commands and not having what we expect makes us nervous... ;-)

[next up - the empty container in Access 2.0 and "where does my code go?"]