Hi!

Main things I remember from my experiense:

Application for SQL Server looks different and function different, thus it requires different kinds of interfaces. There should be no such thing as grid with 10000+ records. When user get results of some serach, it should be limited, for example, to 1000 records until user make search criteria more narrow. SET ROWCOUNT ... command on the SQL Server helps a lot here.

It is wrong that you cannot use VFP indexes advantages in SQL Server application. You can create view, open it with NODATA, index it and than requery it. Now you have all data indexed properly and ready for sorting by different columns in grid.

It is wrong that quick search is not possible for applications with SQL Server. However, it requires more effort with SQL Server.

You will require some way to handle transactions on the SQL Server. Automatic transactions are good only for single data updating. For set of commands and updates under single transaction you will require to use SPT anyway.

You will require to think a lot about security. When you use remote views for your application, you will require to create connectiona and all RV in run-time for best security (of course, if you do not want native ODBC driver logon prompt). With SPT use DSN-less connections string.

Another problem is that SQL Server queries are different than VFP queries. You will require to learn a lot about differences and different functions.

The best way to generate automatic primary key values is to use auto-increment integer key fields. You can get ID value using "SELECT @@IDENTITY" query to SQL Server.

There are a lot of other problems and solutions. Take a look also to articles at the http://fox.wikis.com.

>Hello everyone
>
>Just a quick question as a visual foxpro developer if I was thinking about moving over to SQL Server, rather than having machines processing queries. What sort of problems could I expect ? All I here is SQL Server will solve all my problems, speed, network traffic etc But Ive been in this game to long and know nothing is this simple. So what can the downfalls be? Also is there any point moving to sql server, what size data do I need to justify it etc
>
>Any info would be advantageous, I would rather listen to the people here than other so called experts who are trying to plug a product!
>
>ps currently we use NT/Novell Servers with anything from 5 to 400 workstations.