Well, I've already responded once, but this is ridiculous. A great deal of data is indeed hierarchical. An order has line items. That's hierarchical, but barely. If you have a system with 50,000 or 250,000 orders, are you going to load a treeview with that? It will take forever. And searching will not be easier. Basically this data is flat. It is 250,000 records wide with one level below that. This is not a case for treeviews. Furthermore, if users are just picking packages on the way they look, then I'll be more than happy to skip over that account. It's usability and functionality that count and picking a software package because - wow! - it has treeviews is assinine. Give me a treeview any day of the week where it makes sense to use it and give me a grid any day of the week where it makes sense to use it. Throwing out one or the other without regard to what makes the most sense in a given situtation is really dumb.

Hey - as an aside - you know what is really dumb? I just wanted to check my spelling via the Google toolbar and I noticed it had disappeared. I'm thinking "where did my darned Google toolbar go!" Then I realized I was still logged on to a client's computer via Remote Desktop Connection using IE on that machine and had been surfing the UT and a few other sites that way for over an hour. I guess that goes to show you that RDC over a DSL line is pretty good!


>I am more fasinated with "why" users of VB applications (and technical writers) felt that VB GUI's were more appealing than VFP GUIs. The reason was that VFP developers were selling grid solutions for every project. VB developers did not.
>
>VFP lost a lot of market because of the "grid" mentality and con artists calling themselves VFP consultants.
>
>I went through the "grid" phase. At first the grids were input controls - then they were navigators. Then users began to recognize VFP apps because they saw a grid. VFP's negatives are all associated with projects that overly relied on grids. With SQL it realy got noticable when we took the easy way with grid presented remote views.
>
>If you only know grids (or other bindable controls) you will loose when you compete against me - you will loose when you compete aginst non-VFP developers that don't have grids - but do use OCX.
>
>Not all data are hierarchical
>All data is heiarchial - subsets or the master list can appear as "flat" - but if data were not hierarchial - then we would not need procedural languages - a spread sheet would do.