Not wisdom by any means, just a couple of things to watch for :)

* SQL Server does not support empty dates. In SQL Server they are either 1/1/1900 or NULL. This has great impact on queries where you want to filter by date.

* SQL Server is by default case insesitive. As far as I remember you define how SQL Server will behave when you install it and you cannot change it. I like it case insesitive.

* I am sure you know, but just in case, you must remember not to use VFP functions inside SQL commands that will be processed by SQL Server. You can use SQL Server own set of functions, though.

* SQL commands in SQL Server can be as long as the universe. I love this, you are not limited on how long your statements can be.

* SQL Server is a little bit more strict on SQL statements syntax. There are a few things that you can do in VFP that you cannnot in SQL Server (specially when it comes to GROUP BY and HAVING)


>I've got an upcoming project that is heavily SQL Server. I know that the SQL commands are "supposed" to be standard, but every vendor has their own extensions. Back in the eighties, I worked with Oracle and Informix, and I know enough that whatever it is I wanted to do in Oracle seemed better suited for the Informix extensions, and vice versa.
>
>Now that I've been totally immersed in VFP's version for years, I'm wondering what I'm going to miss in VFP's syntax when I leap into SQL Server. Likewise, what am I going to find out about in SQL Server that you can't do in VFP? Do any of you have any words of wisdom on the differences between the SQL dialects?
>
>Thanks,
>
> - della