BTW Walter... this is a good discussion.. :)

>What about non-c/s envroments (I mean without a database server) ? Second I very much like the idea of having both large datasets in the back-end as the front end: The back-end for transaction purposes, referential integrity, security, the front end for OLAP and reporting purposes (this won't burden the database server in processing trancactions, minimizing concurrency problems). So IMO they're not mutual exclusive. As I said before in a previous conversation, replication of data is a powerfull feature (if possible in your environment).
>

If it is a non-data environment, why bother with VFP? As far asl OLAP goes - ADO-MD handles that in conconjunction with SQL-Server. As far as data replication goes, all the more reason why to use other tools like SQL-Server. IMO, data belongs on the server, and only a minimal amount should be returned to the client...


>
As you said in this thread, we cannot wait for enhancements which are already available in other environments. As we both don't know what VFP has to offer in the next version, I don't draw conclusions on future enhancements. As for the benefits of OO in UI development I don't agree: Much of my personal framework as other commercial frameworks rely on inheritance. Without inheritance I probably would not program in VFP.
>
Inheritance on the UI is important.. And for the most part, the world knows a good deal of what will be in the next version... As for what I know personally, no comment...

Tell me then, despite the fast database engine, am I to conclude that even with that, if inheritance did not exists, you would not program in VFP? It would seem that the fast local db-engine you are trotting out in reality, is not that important...


>
See notes above. IMO C/S and VFP specific data centric commands are not mutual exclusive.
>
Well, if I need stuff like this, I am not cut off from it. Instead of binding it my app logic, I may elect to use a stored proc instead....

>
Could you explain this a bit more. I don't understand why VFP's data centric language cannot play an important role in any layer of a N-tier approach.
>
I did not say that at some point, VFP could not play an important role in one or more tiers...

The point I am making is that VFP does not have the advantages that folks claim it has. The advantages being trotted out are 5+ years old. Guess what, the rest of the world has caught up. Look at the progress VB has made. Match that up with the progress VFP has made. In the past 5 years, VFP is roughly 80% the same product. It would appear the innovations are bypassing VFP in favor of other VS tools...