>>>>My application is built with DBFs
>>>>
>>>>I want to upsize it to SQL Server ... and be able to have the DBF version still working.
>>>>
>>>>I don't know anything about cursor adapters. Would the use of cursor adapters make what I want to do possible?
>>>>
>>>>Would I be able to make an application that would work either with DBFs or Client-server architecture?
>>>
>>>I have several apps that work with either DBF's or SQL Server.
>>>
>>>The way I did it:
>>>1. When you create your .dbf's, make sure the sturcture will work in SQL Server too. (For example, no date fields, no time fields, use only datetime fields)
>>>2. Make another DBC and put nothing but remote views in it to connect to your DBF's. You'll want to use remote views for your entire application.
>>>3. Upsize your dbf's to SQL Server. (If you designed them correctly, NO structure changes will need to be made).
>>>4. Now, if you want to use SQL Server instead of DBF's, all you have to do is change the connection string in the .dbc with the remote views to point to the SQL Server instead of the .dbc with the tables in it.
>>>
>>>This is really a pretty cool way to do it. To change from DBF's to SQL Server you dont even have to recompile.
>>
>>What if your application used browse-like grids for 100K+ tables? Should you recompile it then, or maybe some design change is required?
>
>I was under the impression that a n-tier or client/server apps generally don't allow a person to query 100,000's of data records at once like that.

It is kind of backward logics. Client-server apps don't allow to query/show 100K records solely because they cannot do it in time-efficient way. Fox apps can do it and so they may use it for interface advantage. In other words designing Fox app in rigidly C/S way one sacrifices certain things.