Hi Ken,

You have a couple of options:

1) Use a compound PK with two fields, location and recordID
2) Use a GUID.

Both are good solutions.


>We have a new client who has remote locations. The situation does not call for a wide area network with "on-line" capability. The client would rather give the branch locations the ability to operate on their own and pass data back and forth periodically.
>
>This raises the issue of merging data and the worry about unique primary keys. I have heard about GUID keys as an alternative but, at the time, did not pay enough attention. Anyone have experience with this?
>
>Thanks,
>
>Ken