Mike,

In addition to the answers that everyone has already given you, I would like to point out a few other considerations:

1) SQL Server has no concept of a plain date field: everything is a datetime in SQL Server.

2) Certain VFP functions like sys(2015), which is a favorite for surrogate key generation in VFP databases, do not exist in SQL Server. Keep this in mind when developing your primary keys and their population mechanism.

3) Remote views are not the only way to go. VFP 7 ships with an OLEDB driver for VFP which opens up a possibility for ADO. Simply by changing the connection string in the connection object, virtually everything else can remain the same. I will point out, however, that although you can now execute stored procedures in a VFP database using ADO, those stored procedures cannot populate a recordset: they can only return a scalar value.

4) VFP limits the choice of field types to the basics. However, to optimize a SQL Server database, there are other field types available such as varchar, etc.

I'm sure there are many other considerations to migrating VFP databases to SQL Server, but these are just a few I can think of off the top of my head.

HTH,

Travis

>Hi Guys!
>
>I'm developing an application software using Visual Foxpro 7 and planning to migrate to SQL. Will the SQL recognize the functions of VFP& used in my current application?
>
>Thanks in advance...