>>As Craig said, that may not be the best approach. Besides AutoInc fields you can have a counter table or you can use a GUID (though they are too lonmg as keys for most of my uses :).
>
>
>I guess that I wasn't clear. I have 20 locations that will generate their own Primary Key and then sync the records to one location. This means, at least in my understanding, that I can't use AutoInc, or a counter table.
>
>I could use a 32 character GUID, but I thought that I read that on fast systems it is possible to get duplicate GUID's.

I see now. Different locations then.

GUID: they will not be the same, even in fast systems. Odds are to small for that.
Counter Table: This should work for you if you prefix the counter with a location code. As the PKs are non-meaningful numbers (i.e. who cares if they are in sequence or not), you can have a counter for each location and pre-pend a location number. Therefore you will never get duplicates when synched to a central location.

HTH