> > 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.
>
You use a function called NEWID, do you not? The corresponding function from the "mainstream" MS SQL Server produces a GUID.
http://msdn2.microsoft.com/en-us/library//ms190348.aspxhttp://msdn2.microsoft.com/en-us/library//ms189786.aspxhttp://www.sqlmag.com/Article/ArticleID/49960/sql_server_49960.htmlhttp://blogs.msdn.com/sqlprogrammability/archive/2006/03/23/559061.aspxSeems SQL Server MVPs are into GUIDs.
http://codebetter.com/blogs/scott.bellware/archive/2006/12/27/156671.aspxThe typical answers for many things are wrong, depending on perspective. Having the server generate PKs takes time. An army of client or middle tier CPUs can generate PKs and free the server up for more important tasks. Further the client or middle tier can produce a complete set of hierarchically related records and the server need do nothing, but store them.
Mike Yearwood
www.foxridgesoftware.comPresident: Toronto Ontario FoxPro User's Group