>>Yes I suggest GUIDs. I already hit the problems of integer keys myself and solving them was no fun ( $#@@!#!ed myself a lot why I didn't use GUID from the start).
>>
>Cetin,
>
>What were the problems you run into using integer keys? I am using integer keys for many years, but I too am thinking of switching to guids.

Integer keys are better than the old 10 digit char fields we used to use in terms of size and performance but there are always trade offs.

"Autoinc" in VFP and Identity fields in SQL Server are "automatic" but that by no means suggests they are the best way to do things.

To me the fact that SQL Server provides NewID and SQL Server 2005 provides NewSequentialID indicates that other better options are available.

Funny thing about the following link. They mention security. How likely is it someone can actually determine the next key? They mean only use it on a machine WITH a network card.

http://msdn2.microsoft.com/en-us/library/ms189786.aspx