>>>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.
>
>Then you may read http://fox.wikis.com/wc.dll?Wiki~MoreOnRemoteViews

Yeah I've read though all that a few times before (ha...a few comments from the infamous long-lost JVP in there too). I dunno though, to me creating remote views is super-easy. I also have some classlibs I created a while back that handles all the requerying, updates, conflicts, etc so for me its the best solution. Thus far I haven't had any performance related issues either. I even have one little gizmo I can plop on a screen and the screen's views are automaticly requeried every X seconds while not in EDIT mode to keep the data in sync.
Of course they're very well may be a better way to do this with cursoradapters and I just don't know it yet because I haven't played with them yet.
I just like the idea of being able to change one tiny connection string to switch backends.