FetchAsNeeded and FetchSize for remote views comes to mind.......

>Walter, you've clearly not worked with a backend; you can control the size of data moved from the server, and the client can do things in parallel with the server's continued processing. xBASE command can't - everything must be finished before another, perhaps paralell and disjoint, operation can proceed. This isn't something that requires "batched SQL queries", this is true asynchronous operation, with the client application having the ability to either proceed or pause and waiting on reported completion of the operation. Asynchronous processing is not an option in monolithic single-tier, single threaded environment. The xBASE constructs do not offer this as an option as a native capacity.
>
>>I think we are in total different markets here. My applications are mainly ment for database sizes which do not exeed the 100 Mb limit.
>
>The truth comes out. Your apps don't scale.
>
>>I really doubt that the majority of VFP applications deal with more than that.
>I truly believe you must use C/S technologie, how immature it still is: it is the best way to accomplish this. VFP can provide a front-end and/or middletier and use some limited datahandeling on the DBMS side. Of course this depends on more than only just the DB size.
>>
>
>Walter, here you demonstrate that you don't understand what client-server technology is. Every one of us operating in a network environment has a reliance on client-server technology. Every one of use who relies on the service of one application to meet the needs of another makes use of the client-server paradigm, every damned day of our existance. If client-server were more than a buzzword to you, you'd realize this.
>
>Client-server paradigms exist in more than the database backend environment.
>
>Yes, I use client-server technology. And I know when and where it's appropriate.
>
>>>My perspective here is that I like having tools that take advantage of otherwise idle cycles to analyse the history of user requests and try to. It's inevitable that given a system that is not overburdened, there will some useful and usable idle time available to expend on lower priority tasks that can be performed in part or whole asynchronously in anticipation of future user requirements. If you guess wrong about what will be needed in the future, you're no worse off than if the system just sat there and twiddled its thumbs.
>>
>>I think their is still lot's of room for improvements of RDBMSs, and I truly believe that they will show some features already accomplishable within xBase (VFP) in the near future. An example of one feature implemented some time ago in SQL-server is the handling of server-side cursors which provide some record based mechanisms.
>>
>
>I don't argue that database technology is fully developed, but it is not stagnant. xBASE and procedural language constructs OTOH are. SQL is not solely an RDBMS technology; in fact, it serves to virtualize the underlying mechanisms used to store and retrieve data. SQL can and is applied equally well to services provided by tools that rely on other data models (IMS, for example, is a hierarchical model backend that has a SQL interface available; ObjectStore is a pure OODBMS that is closest to a network model implementation, and it, too, supports SQL operations.) Utilizing SQL allows the data manipulation technology to grow and change without having to radically alter the approach to data manipulation; xBASE is inherently reliant on explicit index-based operations, and is incapable of adaptive behavior without programmer intervention.
>
>I'll reserve judgments on the immaturity of the technology until someone with greater experience with and understanding of the theoretical and actual capacities makes a statement. You don't meet the requirement. To use a bit of street slang, you don't walk the walk, and can't even talk the talk.
>
>>Until, RDBMS provide the same technology as xBase languages, I'll be forced to use commands like SET FILTER, SET RELEATION etc..
>
>Don't let me stop you, just don't misrepresent yourself as having the expertise to know when and how the technology and capabilities are present.