Found one interesting link myself;

http://download.microsoft.com/download/c/c/f/ccfb0626-5629-42c6-8e0c-9bc89a76fd3a/SQLServer2000ROIreport.pdf

Aldough sligtly pro (MS)SQL Server biased, it offer some analysis
points to consider, when doing your cost calculations for backend database
that will be incured to you and/or your clients.

Keep on searching...

>Dear all,
>
>If you have converted from VFP to NET already, or you are doing it right now and you also happen to use SQL server as back end database ;
>
>It wld be interesting to all of us who are still only with VFP, if you
>could provide some transitional figures in terms of ;
>
>1. Time to get *comfortable* with NET.
>2. Time to create your own, or adopt workable commercial framework
>(Not to someone like RickS, or BonnieB or meny respectable others,
>but to a regular senior level VFP person.)
>
>3. Time for conversion/development of typical VFP custom project.
>Let say, ordinary sales-invoicing application, involving standard reporting
>with some typical yearly/monhly/weekly/summary sales figures being derived
>from the system and presented to the user.
>Client/Server app deployed on LAN.
>
>4. Typical SQL licence costs for S2M/L enterprise clients (0-25, 25-100 ,100+ )
>
>5. Typical Hardware Upgrades required for clients.
>
>6. SQL Administration/Maintenance costs.
>
>Not exact figures but at least something that can help us make at least rough estimates of costs involved.
>
>Links to articles sheding light to this time/cost issues, would be also helpfull.
>
>Any other honest/true VFP->NET conversion story/input is welcome.
>
>Fishing/Hunting/SexSuccess story tellers to abstain :)
>
>TIA