Terry

I'm not saying only use SQL, I am saying don't discount it. What is "sexy" is completely personal preference and I've grown very tired of that phrase.

>>>You seem to constantly discount using SQL and that's a mistake.
>>>
>>>And furthermore:-), an over reliance on SQL syntax and other "batch" methods, lends to the dilution of our iterative skills.
>>
>>I said nothing about over-reliance on SQL. In your case you seem to over-rely on xbase ONLY. That's a mistake.
>>
>
>I don't see why? My projects flow in and out of all sorts of controls. They are faster that a apps that do the same samething in SQL. The screens are faster - the projects are not cluttered with refresh-s and re-queries. If the app is faster - and the xBase libraries evolve leaner and meaner and they can compete with projects developed in other tools why is it a mistake. The mistake may be to deny xBase and iteration (which - admittedly - requires more "practice" and "conceptual" discipline than SQL).


>
>Why were VB apps slamming VFP development? Because the VB interface did not have cursors and and grid services that allowed willy-nilly selects on a whim. The VB developer had to reiterate through a record set and add the data to an activex list control. The VB guys were beating us up because many of us were cascading grids via selects as the primary motif for interface behavior.
>
>A feature that is less "challenging" conceptually or only takes few lines of code usually cannot compete with projects that take advantage of "more" discrete low level processing.
>
>What do you prefer - a grid or a listview. Listviews are sexier. To feed data to a listview or Treeview with SQL - first you select into a cursor (eat resources) then you may have to index or select into more cursors (eat more resources) then you have to scan through the temporary cursoers and reiterativly "add" the nodes. With a well planned xBase solution, the project only needs to cycle through existing (and already opened) tables. At some point - to develop compeditive apps with activeX controls the develeoper needs the record pointer. Why not just design the entire app that way?

Because at some point the developer needs to interface with SQL Server for one. All I'm saying is don't chose one way over the other. You're chosing non-SQL only. There are certainly places where SQL outperforms xbase and vice versa.