>Is client/server beneficial beyond data security issues for few, 8 or less, users? I read something lately that said vfp downloads all of a table's records regarless of the SQL where as client/server does not. Also, is Fast Ethernet much of an advantage over 10 mbs Ethernet in small multi users environments? The hardware and cabling cost is not much more but if its a waste that would be good to know. Thanks
>John


Here's my 2 cents worth ....

The number of users really has nothing to do with it. The AMOUNT AND TYPE of DATA you're transmitting over the pipe does. You could have 2 users that can fill the bandwith or you could have 200 that doesn't. Generally, database applications are 'bursty' unless you're pushing or pulling some type of graphic or other large files continually. It sounds like your questions are simply about bandwith and you should take a look at exactly what your applications are doing to the bandwith of your network. There are tons of tools out there for this but I've found the Performance Monitor to be a good starting point.

For many of the networks I administer (and have my programs running on) I've found the best speed improvements (after optimizing the applications themselves) have come from going to a client/server or n-tier structure and not going to a fast ethernet or giga ethernet pipe. There are still not many machines out there that can fill that kind of pipe consistantly. You're usually better off going with some kind of switches so you can get dedicated 10 Mbs to each and every machine instead of 100 Mbs shared among them all.

There are many more good reasons for going to a client/server or n-tier structure beyond bandwith preservation as the others have mentioned already. But you also add more levels of complexity to the design. You can't get something for nothing it seems. :)


Good luck.

- A Hilton