>Hi Bill....
>
>A few compelling questions to ask...
>
>1. Do they need the integrated security?
>2. Do they need more robust replication capabilities?
>3. Do they need a more robust engine with full support of Stored Procs?
>
>
>If your app is the only thing accessing the tables, they don't care about integrated security - VFP may be the best choice now. Going to SQL Server only increases your headaches.
>
>The compromise I would strike for is to hold the data engine constant while upgrading. But...build the new app with an n-tier mindset so that elements like ADO and SQL Server can be used instead.

To answer your questions, No, no and no<g>.

I'm using views for most all queries, a la Codebook. But it would still be quite a rewrite for SQL Server, simply because I'm taking advantage of VFP's capabilities. You should have seen the other guy's eyes light up when I told them I was using views for this app -- Aha! We use SQL Server in place of the views -- the rest is just implementation<bg>.