>George:
>
>I can see how an auto increment column may make it easier to work with VFP data, but don't see any benefit for working with SQL Server. Actually, I don't like the auto increment feature of SQL Server because you have to always make an additional round trip to server to get new key back to client when adding a record. I pefer to use a stored procedure to generate unique keys. In my framework, only one trip to server is ever made to get a unique key. At application start-up SP is called and key is returned, subsequent keys are generated on client by concatenating startup key with key created on client saving many round trips to server.
>
Charlie,

It isn't just auto-increment itself that was the premise of my post, it was the implication of it. That it was "the tip of the iceberg" in regards to bringing VFP closer to SQL Server in order to create an environment where you would have significantly less work to do to upsize an existing application to SQL Server provided you made the right design considerations.

Even at worst (as I posted to DD) some of this immediately comes to fruition with this feature.