>Hi,
>
>For me I normally set the length only base on my estimation on how large the table probably will grow.
>The larger the lengthier, things like 10, 12, 16, 24 or even 32 chars in length.
>
>I wonder what are the key factors everyone else is considering when trying to determine the length of a GUID field (let say it is used as primary/surrogated key field of tables).
>
>Is there any good article out there discussing how should one decide the length of a GUID field (be it a sequential one or non-sequential)?

I use an Integer (4 bytes); the number is sequentially assigned, from values stored in a table. The concept is similar to the AutoIncrement, but I designed this in an older version of VFP (and I prefer to keep the control of the sequential numbers myself, so I keep my old system).

GUIDs are useful if users are not permanently connected. GUIDs are supposed to give unique values (based, in part, on the fact that each network card has a unique serial number). However, GUIDs are fairly long - 16 bytes.