Though I'm not a fan of .NET nor of the people doing .NET that have to stay here and snipe at VFP, I'd have to say that I can't agree with your fascination with treeview controls. They have a place, no doubt. I have used them to great effect when the data is truly hierarchical (Bill of Materials for instance, where an assembly can be made of multiple assemblies and parts and the depth may be 3 or 6 or 10 levels deep). There are other situations where they are also quite handy, but a grid is my primary tool. I use it for finding records (click on the List tab, which displays multiple fields from the main controlling table with some or all columns being speed searchable - navigate to the desired record and press Enter to show the main tab where a single record - and child records in a grid, perhaps - is edited). This is a great way to find records most of the time and when more advanced searching is required, I also offer a search tab. And grids are a great way of adding "line item" data like line items on an invoice, sales order, etc. Direct editing in the grid, not just using it to bring up a child form where one records's fields are edited before you have to save and go back to the grid to select another record for editing in that same child form (that's the method some people recommend - even some of the "gurus" - but it's garbage and much harder for the user - direct editing in the grid is the way to go). Regardless of how much people use computers, they still use paper a whole bunch, and a grid more closely simulates paper-based forms than does a treeview. I really love treeviews in the correct situations, but I find the grid is more practical on a day-to-day basis.

>Grids have been around since the 80's - they're so yesterday - and forms with page frames - one page for entry and another with a filtered grid search are so yesterday.