> Well they say if you ask 10 computer experts a question you'll get 10 different answers. Unfortunate for all of us, IMO.
That's true. But remind me about one thing, which databases actually implement GUIDs as options for Primary Keys i.e. Autogenerate the GUID when a new record is added. I am pretty sure that none of he mainstream databases support this (i.e. Oracle, SQL Server, DB2 and so on). Maybe the "new" clones do so - MySQL? Postgres SQL?
Remember, just because you CAN do something, doesn't mean that you SHOULD.
> #3 Not for a merging - I'm talking more about a corporate merger. If branch A had a completely different set of customers than branch B, the use of numerics in each branch would absolutely require our intervention. With GUIDs we could just append one set of customers to the other.
Dont see that it makes any difference really, you just use a surrogate integer PK on the merged table and drop the original ID - the GUID (which is not the PK in the merged table) is still the link back to the original. Whether you use the GUID AS the PK in the merged table is completely irrelevant in this context - you still need it, yes, but it does not matter whether it is also the PK or not.
Regards
Andy Kramek
Microsoft MVP (Visual FoxPro)
Tightline Computers Inc, Akron Ohio, USA