>
>I agree completely. I have developed a few apps over the past year in VFP5 and now certain people in the company are suggesting we go to c/s. My question to them each time is, Why? They have no clue, except that it's the latest buzz-word, and matter of factly neither do I.
>
>So, what would be good reasons to make a business case of moving to c/s? Personally, I would like to know because maybe our environment would be a good fit for c/s, but I'm definitely not doing it without any real info.
>
>Any thoughts would be greatly appreciated.

IMHO, the two most overriding factors would be contention and security. If there are a large number of users, trying to modify the same records (say an inventory table), or if the data was sensitive (employee pay information). C/S might be a better choice. This is not to say that VFP Database couldn't handle it, it could. Further, if cost is an issue, a VFP application is an obvious choice.