Kirsten has lots of tables already created with traditional PK IDENTITY columns, so I'm guessing that converting the PKs would be a nightmare. Perhaps a compromise is the answer: add an indexed Guid column to those tables that might find it useful in sync processing. That Guid is effectively "stamped" onto the row and never changes even if the INT PK does. I did this years ago to some of my own tables and they're still in use and the Guids are used by external applications to reliably and unambiguously find rows.
However, can Sync Framework make use of Guid columns that are not the actual PK? Greg
