I think a lot of that paper still applies today except for the addition of MSDE - a free, dumbed-down version of MS-SQL. MSDE adds a layer of complexity to development and deployment, but, could be the right choice if there's ever a possibility of going to full-blown MS-SQL in which case the switch is pretty transparent...
>The following text was extracted from a white paper published by Microsoft, in 1996, written by Robert Green.
>
>"Microsoft® Solution Providers and MIS developers often ask the question: "Which Microsoft tool should I use to build this database solution?" In most situations, virtually all of the Microsoft tools can be used effectively. Nevertheless, each tool has its relative strengths. The purpose of this paper is to help developers choose the tool best suited to their needs. In particular, this paper will examine Microsoft® Access 97, Microsoft Visual Basic® programming system, Microsoft Visual FoxPro™ database management system , and SQL Server™. Mention will also be made of Microsoft Visual C++® development system and Microsoft Visual J++™ development system."
>
>It proved to be indeed helpful, be it to help the (FoxPro) developer to choose the appropriate technology to use in an application on design, be it to "convince" IT managers where VFP (and the accompanying DBFs) are the right choice.
>
>Unfortunatelly that white paper is outdated and no more residing in MS web site.
>
>Should it, please, be possible for the Fox team to prepare another white paper to have the same applicability and help us (VFP developers) to respond that damn question, asked every day?
>
>Does any of you have some comments about this issue? Please, post your comment, I know you understand the problem I'm facing :)
>
>Fernando
>
>PS. The Q & A section and Appendix D ("Database Engine Features Comparison") really help! (could be a *very* good start)