>
>1) Use a compound PK with two fields, location and recordID
That makes it a compound key!
>2) Use a GUID.
This is what I would suggest. It does not require compound primary keys and no maintenance if more location get added
I believe there is a API call to get the GUID
Peter
Peter Cortiel