VFP will not be dead in 2 years. Even if MS are thinking about killing it, look how long it took them to stop supporting 2.6 - about five years after VFP came out.

SQL Server will mean more development teams, meaning more (and more and more) money. You will get the SQL team waiting for the front-end team on one thing while the front-end team waits for the SQL team for something else.

I'm not saying that multi-tier development is bad and too costly. But I think in your situation, it will be a complete waste of resources. Somebody would have to trawl through all your code to find the validation rules and then decide whether they should go in SQL or the front-end. All this before anybody even begins development.

Alternatively, they could just go at it with a big hammer and get it working that way :)

If I was being told that SQL will be the best alternative, I'd have a long list of questions to ask the person telling me. Like who told you VFP will be dead in two years and what are their qualifications for telling you that.


>My question(s) for you is, do you think Visual is going to be dead in 2 years, do you think that Visual running 2.6 Windows code will be stable enough to work, what is your opinion on using SQL Server with these size databases, what are the ongoing support/other costs involved with SQL Server that maybe my client does not realize will be there in the future and any other opinions.
>
>Thanks for time on this.
>
>REC Computer Systems