>as Jim already said, generating GUIDs out of another value is not possible. But IMO they won't do you too much harm, besides they are consuming space (32 Bytes in a VFP table stored as string and 16 Bytes when stored in SQL Server). In a VFP table you can set a default value function that returns a GUID and in SQL-Server you can use a built in function. So they won't afford any other coding.
>
>BTW: I find GUIDs a very good approach for PKs. They are unique without any ID tables, can be created with a simple function call and can be generated totally offline or in the database.

As more and more applications are talking with other ones, do you think that more database design will go in favor of a GUID approach for their primary key as some of them will travel across the wire to end up in other applications?