> After the long dicussion, I would like to ask, what development tools should be used for each tier?
<

In the C/S arena, for me it is SQL-Server on the back-end. VFP cursor don't scale. As a medium for local processing and presentation, they are fine since we are talking about an extremely small subset of data. As a primary data store, I don't use DBF's any more.

In the middle tier, it depends on what you need to do. If I need to do some hard-core data processing, VFP would probably be the best choice. If you don't need a lot of data processing and/or don't have a need for the capabilities of local VFP cursors, a scenario where most C/S apps fall, the incentive to use VFP comes into question for me. Ultimately, for whoever it is, if VFP is the tool they know, it is a moot point in that VFP is what they use. That however, does nothing to address what technically may be a better tool. Then again, issues of practicality to me are often more important that what may be technically better. A point that is lost on a lot of 'OOP-Purists'. If you need to make use of events, or need better support of API calls, the tide starts to go in VB's direction.

>Or how do you design n-tier application with development from choosing development tools?<

The design should be independent on a tool. That is biggest mistake made today. Regardless of the problem, the design is driven by their choice of tool. I think every dev community is quilty of this.

<
If possible, would you have an article or whitepaper that talk about the development tools for C/S, issue that should be consider on C/S and so on for each develoment? I think is is great to have this article for reference in future......
>

I might write a paper that breaks down the whole VFP vs. VB argument...