> From: Guillermo Najar-Arreola [mailto:gnajar@...]
> Sent: Wednesday, August 28, 2002 4:50 PM

> Object Identifier:
> http://www.AmbySoft.com/mappingObjects.pdf

> ""Leyne, Sean"" <sleyne@...> wrote in message
> news:66187D861C1747499BE1365B74E0369110ACCC@......
> >
> > OIDs???

Oooohhhh, an ID!

I would then suggest that you kill '2 birds with one stone' and use a
GUID as your primary key.

They are pratically unique for any computer (_mathematically_ possible
for 2 computer to generate same value, but extremely, extremely remote).

So, you don't need to worry about creating a componound key.

Also, unlike a generator, the value can be calculated outside the
database -- so your app knows the key value (for master-detail
structures) and you don't need to access the database to determine the
value (ideal in WAN environments).


Sean