>>>>>>>>>>>>>>>
There is the old true and tried method. I've seen UNIX shops with FoxBase/FoxPro serve 400 users.
Place you DBC or free tables on serverdirectory. Put your exe/runtime at the desktop. Have the desktop runtime point to the server tables. The more 'real-time' your app is (ie the less it relies on batch methods), the faster it will run.
>>>>>>>>>>>>>>>

Terry,

That is not a C/S architecture which is what the original question was about. Your solution is still a monolithic EXE using drive mappings, where all records travel through the wire. I'm not saying it is a wrong approach (it depends), just not C/S.

For C/S with VFP you must use ODBC (OLEDB will be available in VFP7) and a connection (in code or DSN) pointing to a database server. VFP works through ODBC but it is not that great. A true C/S database like SQL Server (or MSDE, Oracle, etc.) is needed. Then processing is done at the server and the only records that travel through the wire are your record sets (results).