>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

Thanks for the tips.

I have developed the product (a timeshare resort reservation system) and am paid by the hour. The customer and I share ownership of the software.

I imagine that I and the system engineer would be the only techies involved in bringing in SQL Server. No additional consultants. My software is fairly unique and gets the job done 24-7. Very unlikely they could be talked into ditching it.

They also use software from Siriusware which is written in VFP. I believe that helps them trust VFP.

Peter