Peter,
>>They have deep pockets and an overworked system engineer. I bet they will go with the MSFT solution. :-)
Sounds like an excellent prospect for C/S. A word of caution: is the customer using a product you own? If not, be careful who you invite into the hen-house, unless you want to find yourself competing for the whole business against somebody expounding the MSFT party line. Before you get SQL people involved, at least discuss issues like dotNET with the customer... if a rewrite is in order, the reasons you propose to keep the UI in VFP rather than dotNET are the following... retention of "tried and true" business logics, familiar screens etc etc so you can't be portrayed as a luddite by hungry consultants who think they might like all the business, not just the parts you send their way.
Regards
j.R
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
