Enabling Identity Partitioning
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
If you use identity columns in your database schema and want to make it possible for multiple users to take the solution offline, you must enable identity partitioning for your offline publications.
When designing tables in SQL Server, you have the option of enabling the Identity property for a column. Identities are incremented by SQL Server automatically as new rows are added, similar to an autonumber field in Access. If you do not use identity partitioning for your offline publications, two users who both take a team solution offline and add rows will have conflicting identities when they synchronize. Because other records may refer to this identity as a unique identifier, you do not want this number changed during synchronization.
By partitioning identities into large ranges for multiple users, the likelihood of conflicts is virtually eliminated.
To enable identity partitioning
Open your solution in the Access Workflow Designer. For details, see Opening your Solution in the Access Workflow Designer.
From the Access Workflow Designer, select the team solution in the Object List.
In the Solution Properties pane, select the Offline tab.
Select Enable identity partitioning to enable or clear the option to disable this feature.
Click Save.