>Three years ago that I work with a VFP database to handle the
>administration of a public service company. Currently my data base
>consists of a millon of records approximately. As the
>database is growing so much in the last months, I decided
>to buy Ms SQL Server 7.0 to begin to study it, and thereinafter
>upgrade my application.
>While I advance with the study, realize me that a lot of "novelties" of SQL7, already exist in VFP and , some Transact SQL commands are equal to VFP (soundex,difference, etc).
>Furthermore, the trials that I have accomplished, they are much but slow in SQL that in VFP

Depending on how you manipulate the data. Remember, there are several ways to manipulate RDBMS data: RV, SPT, SP, ADO. In some cases, it's a bit slower because SQL Server is not native to VFP.

>The questions are:
>It is so complex that it can be implemented by a simple experienced VFP programmer ?

It's a matter of familiarity and transition time i guess. But in the end, a sigh of relief will come on you because your data will be secured enough.

>Only is justified the migration for networks with thousands of transactions per minute?

Learn to combine SP - server side, and data intensive COM - where VFP has its strength. Don't manipulate RDMBS data totally equal with how you manipulate VFP native tables via RVs. What we do is a mixture of the two: VFP table for static data while SQL Server for transaction data.