>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.

>
>Without, or lessened iterative (record pointer) skills, we may be less apt to develops solutions using ActiveX. ActiveX requires well developed iterative understanding because they cannot be "batch" bound to a control. Even base class controls that are bound, if I remember my earlier readings correctly, are problematic with drag and drop (when bound) - and usually perform best with "additem" syntax.
>
>Granted - the ease of SQL selects is a benefit. But, an over reliance on those kinds of features can deny our projects those really cool OCX controls the discriminating user has come to appreciate.
>
>If our market is like the old days when a "custom" program was not required to compete with the "shrink wrapped" solutions, it was easy to get away with SQL solutions. But - if the user had a choice between SQL selects into a cursor to feed a "grid" and an iterative solution to that feed a treeview or listview, it is an easy bet the user would choose the latter.
>
>Maybe I compete in a different market than yours. But my users want OCX.
>
>The solution will always perform better when the discipline of conserving resources practiced.