>Bonnie,
>
>>We'll soon be implementing a multiple location scenario and will be dealing with ranges of keys for each site. We opted from the very beginning to not use GUIDs because of their size, so we use integers (actually SQL Server bigint, just to play it safe <g>).
>
>Yep, I've seen and done both, and each approach has its strengths and weaknesses.
>
>Some well-known development shops always use guids and some always use integers. My original point was just that surrogate keys don't have to be integers.

FWIW, in my original post I said, "should be" not "have to be".