>>>
>Point is in .NET you are encouraged to keep the amount of data small, In VFP this is much less an issue.
>>>
>
>Duh..... Fox is based on a file-server paradigm and .NET is based on a distributed C/S paradigm.
>
>And yes, in Fox it is an issue when you try to open a dbf over the wan - as you have zero control over what gets passed to the client. Being a file-based system, it makes for a lot of network overhead - bring more information to the client than you really need. Fox needs it becuause that is the way it works.
>
>Finally, if you are using VFP with Oracle, SQL Server, etc, you are encouraged also to render small data sets back to the client.
>
>You really don't know what you are talking about Walter...

Think again, john...

You can't read what I'm saying here. It never did say where the data was comming from. You can generate an awfull lot of data from just a little you download from any database server.

You can generate lots of meta data on your client for whatever reason. VFP does not care. .NET does as all records sets are to be held in memory.

The fact is that in VFP you can handle lots of data efficiently without the workstation bogging down (because data is flushed to disk in temp files), no matter for what reason you've got lots of data loaded into your client.

John, Lets face it. It is no use, You can't win this. It is you who can't read what a message says and understand what I'm saying.

Poor soul...

Walter,