>>Hooray!
>>
>>Oh it does lift the faintest of hearts to see there are others who realise that Client/Server isn't the *only* option. Even if saying that developing client/server apps gives you more kudos in the pub < G >
>>
>>Speed is the key - as the Sugar Cubes put it. I like responsiveness but I will go with a Client/Server solution *only* if I feel it is the right thing to do.
>>
>>Cheers
>>JR
>
>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.

IMO, c/s is preferable for busy interactive environment, if let say you have more than 50 users which spent more than 50% of their time really editing (not viewing) or adding records. Obviously, these numbers are pure speculations.