>I'll ignore your ranting for your own sake.
Again does not sounds right, but is at least reasonable decision.

Anyways, let us:
------------------
set rant off.
set attitudes off
begin conversation
------------------

As a parting shot, just remember it takes more than three months to evaluate .NET.

Agreed / Need no discussing.

Now;
Since you converted to NET already, It wld be interesting to all of us
who are still with VFP, if you could provide some transitional parameters
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 PaddockR or BonnieB , but to regular senior VFP level)

3. Time/Complexity for conversion 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.

4. Typical SQL licence costs for SME/LE clients (0-25, 25-100 ,100+ )

5. Typical Hardware Upgrade costs required for clients.

6. SQL Administration/Maintenance costs.

Not exact figures but at least something that can help someone like OP,
or me make gross estmates of costs involved. I asked CraigB already about this, but I got declined figures due to non-disclosure reasons.

Since you already published some of your real figures, I hope you will be
able to provede us with some aproximate figures as per above list.

Links to articles sheding light to this time/cost issues, would be also helpfull. That would be really constructive/helpfull from your side to all our felow foxers.

Any other honest VFP->NET coversion story is welcome.

Fishing/Hunting/SexSucsess story tellers to abstain :)

TIA

Will as a matter of fact start new thread about this so you
can respond there as well.